ci: modernize NuGet publishing workflow#2
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
gh release createcontents: readand grantcontents: writeonly to publishingWhy
The existing workflow used three Node 20 actions and pushed its version commit and tag before build, pack, and NuGet publication had succeeded. A failure could therefore leave repository release markers for a package that was never published.
Validation
actionlintv1.7.7dotnet restore src/Ytxdotnet build src/Ytx --configuration Release --no-restoredotnet pack src/Ytx --configuration Release --no-buildnupkg/solrevdev.ytx.1.0.3.nupkgcontentsThe repository has no test project, so there is no separate local test suite to run.