ci: create a GitHub Release on tag#192
Merged
Merged
Conversation
The release workflow published packages but never created a GitHub Release. Add a step that runs 'gh release create' for the pushed tag with auto-generated notes and the .nupkg files attached, flagged as a prerelease when the tag has a -beta/-rc suffix. Requires contents: write.
The packages are on nuget.org and GitHub Packages; the release only needs GitHub's automatic source archives, so drop the .nupkg assets from gh release create.
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
1 participant
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.
The release workflow pushed packages to nuget.org + GitHub Packages but never created a GitHub Release (the tagged entry on the Releases page). Add a final step:
-beta/-rcsuffix, so stablev4.0.0becomes 'Latest' butv4.0.0-beta.1does not.contents: write(added).Applies to future tags.