Summary
There is no automated workflow to publish new versions of BuzzSpire.Nexar to NuGet.org. Releases are presumably done manually, which is error-prone and inconsistent.
Problems
- No standard release process defined
- Risk of publishing with incorrect version or missing artifacts
- No audit trail for who published what and when
Proposed Solution
Add a GitHub Actions workflow that triggers on a new GitHub Release tag and automatically publishes the NuGet package.
on:
release:
types: [published]
jobs:
publish:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- uses: actions/setup-dotnet@v4
with:
dotnet-version: 9.x
- run: dotnet pack --configuration Release
- run: dotnet nuget push **/*.nupkg --api-key ${{ secrets.NUGET_API_KEY }} --source https://api.nuget.org/v3/index.json
Requires adding NUGET_API_KEY as a GitHub Actions secret.
Summary
There is no automated workflow to publish new versions of
BuzzSpire.Nexarto NuGet.org. Releases are presumably done manually, which is error-prone and inconsistent.Problems
Proposed Solution
Add a GitHub Actions workflow that triggers on a new GitHub Release tag and automatically publishes the NuGet package.
Requires adding
NUGET_API_KEYas a GitHub Actions secret.