This is the first release of an action that checks the availability of a .NET package on NuGet. just go ahead to try 💪
nuget-package-check-action
- Automates NuGet package availability checks, ensuring packages exist and are indexed on nuget.org.
- Supports multiple verification attempts and can suspend CI/CD workflows until the package is published.
How to use
✅ To quickly check if the package exists and is available on NuGet, please add the following job:
- name: Check Available NuGet Package
uses: BMTLab/nuget-package-check-action@v1.0.0
with:
package: YourAwesomePackage
version: 1.3.505
✅ If your workflow publishes a package and further work requires that the package is already available and indexed,
please set a reasonable number of retries:
Tip
The retry interval is 30 seconds,
so 10 retries are usually enough time between publishing and when the package is indexed and available.
- name: Check Available NuGet Package
uses: BMTLab/nuget-package-check-action@v1.0.0
with:
package: YourAwesomePackage
version: 1.3.505
attempts: 10
❌ The job will terminate with an error if no package is found.
Compatibility
Ubuntu | Windows | MacOS |
---|---|---|
✅ | ✅ | ✅ |
Important
When you're using self-hosted runners, please make sure you have Node.js v20 installed!
Contributing
Please feel free to contribute or let me know if you find a bug.
Also, any ideas for improvement would be appreciated 😇
What's Changed
New Contributors
Full Changelog: https://github.com/BMTLab/nuget-package-check-action/commits/v1.0.0