Repository navigation
Publish a release when a new version reaches master - #66
Merged
Merged
Conversation
Tagging needed someone with push rights at a terminal. Now the release workflow also runs on pushes to master: if package.json has a version with no release yet, it runs the tests, creates the tag on that commit and publishes the release. Pushing a v* tag by hand still works.
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.
What does this change?
Until now a release needed someone to push a
v*tag from a terminal. This PR adds a second trigger to the release workflow: pushes tomaster.On a push to
masterit checks whether thepackage.jsonversion already has a GitHub release:gh release create --target) and publishes the zip and tar.gz with the changelog section as notes.Pushing a
v*tag by hand still works as before.docs/RELEASING.mdnow describes the flow: merge a "Release x.y.z" PR and the release is published.masteris already at 2.1.0 (#65) with no release, so merging this PR publishes v2.1.0.How did you test it?
node scripts/release-notes.js 2.1.0prints the right sectionmaster, so merging this PR is its first runGenerated by Claude Code