Repository navigation
ci: create GitHub Releases from CHANGELOG.md on version tags - #27
Closed
NishantJoshi00 wants to merge 1 commit into
Closed
NishantJoshi00 wants to merge 1 commit into
NishantJoshi00 wants to merge 1 commit into
Conversation
Add a release workflow that runs on the same v* tag push as the crates.io and npm publishers and creates the GitHub Release with notes taken from the matching CHANGELOG.md section. A tag whose version has no changelog section fails the job, so no release ships without notes. Backfill CHANGELOG.md for v0.1.0 through v0.12.1 from the commit history, add homepage/bugs metadata so the crates.io and npm pages link back to the repo, and teach the release skill the changelog step. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
2 of 5 tasks
Collaborator
Author
|
Superseded by #28. |
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
releaseworkflow: on everyv*tag push, creates the GitHub Release with notes from the matchingCHANGELOG.mdsection plus crates.io / npm / docs.rs links. Fails the tag if the section is missing.CHANGELOG.mdbackfilled for v0.1.0 through v0.12.1 (Keep a Changelog format), with an Unreleased section for the commits since v0.12.1.homepage/bugs/keywordsinpackage.jsonandhomepageinCargo.tomlso the npm and crates.io pages link back here.Test plan
.github/scripts/release-notes.sh 0.12.1prints the section;9.9.9exits 1🤖 Generated with Claude Code