[codex] Create GitHub release after NuGet publish#83
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
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.
Summary
v{packageVersion}GitHub Release after NuGet publish succeeds.package_versionas an output from the package smoke-test step.CHANGELOG.mdsection and create an annotated tag before publishing the GitHub Release.Why
Publishing to NuGet and then manually creating a tag/release can leave the repo in an inconsistent state. This keeps the manual dispatch gate, but makes the workflow finish the release metadata once the package has actually published.
Validation
git diff --checkruby -e 'require "yaml"; YAML.load_file(".github/workflows/release.yml"); puts "yaml ok"'0.1.0sectionNote:
shellcheckis not installed locally, so the embedded Bash was inspected manually.