feat(ci): auto-tag and release on version bump to master (v2.4.3)#9
Merged
Merged
Conversation
Previously a release required pushing a `v*` tag manually, and a
separate gate-release job verified the tag was reachable from master.
Drop that whole flow in favour of a simpler model:
1. PR is opened: matrix runs for verification only.
2. PR merges to master: matrix runs again. If every job succeeds AND
the package.json version on the merge commit has no matching
`v<version>` tag on origin yet, the release job:
- creates the tag pointing at the merge commit
- creates a GitHub Release named after the tag
- uploads the prebuild tarballs as release assets
The tag is created by softprops/action-gh-release using the
built-in GITHUB_TOKEN, so it does not cascade back into the
workflow.
3. Master push without a version bump: matrix runs, release step
sees the tag already exists, skips. No-op release.
Cutting the first release of this flow by bumping to 2.4.3.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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.
Previously a release required pushing a
v*tag manually, and a separate gate-release job verified the tag was reachable from master. Drop that whole flow in favour of a simpler model:v<version>tag on origin yet, the release job: - creates the tag pointing at the merge commit - creates a GitHub Release named after the tag - uploads the prebuild tarballs as release assets The tag is created by softprops/action-gh-release using the built-in GITHUB_TOKEN, so it does not cascade back into the workflow.Cutting the first release of this flow by bumping to 2.4.3.