Repository navigation
ci: create the GitHub Release from the CHANGELOG when a tag is pushed - #4
Merged
Merged
Conversation
Same flow as the other repos in the harness (tag v*.*.* extracts the matching CHANGELOG section into a Release), minus the registry publish this module does not have. It also checks the tag against Capabilities::VERSION and fails on an empty section. workflow_dispatch with a tag releases tags pushed before this existed.
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.
Adds
.github/workflows/release.yml, the same flow the other repos in the harness use: pushing av*.*.*tag turns the matching CHANGELOG section into a GitHub Release (softprops/action-gh-release@v2, name = tag,generate_release_notes: true). There is no registry here, so it stops at the Release. It also checks the tag against the project version and fails on an empty CHANGELOG section.workflow_dispatchtakes an existing tag and runs the very same steps, which is how the tags pushed before this workflow existed get their Release.Verified: the workflow YAML parses, and its shell steps were run unchanged against the real tags (notes extracted and the version check passes for every existing tag; a deliberate tag/version mismatch fails). The workflow itself only runs on a tag push or a manual dispatch, so CI on this PR does not exercise it; its first real run is the dispatch after merge.