Repository navigation
ci(release): release by merging a VERSION bump - #15
Merged
Merged
Conversation
Merging a PR that changes VERSION now tags the merge commit v<VERSION> and runs goreleaser in the same job. A tag pushed with GITHUB_TOKEN doesn't start another workflow run, so the build can't wait for the tag trigger. If .github/release-notes/v<VERSION>.md exists, it becomes the release body instead of the generated changelog. Pushing a v* tag by hand still releases as before. This lets the release be a reviewable PR, and lets automation that can open and merge PRs but can't push tags cut releases. VERSION starts at 0.2.2, the current release, so merging this PR tags nothing. Co-Authored-By: Claude Opus 5.5 <[email protected]>
Merged
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.
Why
A weekly Claude routine will review PRs and cut releases for this repo. Cloud sessions can open and merge PRs, but they can only push
claude/*branches, not tags. Right now a release only happens when someone pushes av*tag by hand.What changes
VERSIONfile, set to0.2.2(the current release).release.ymlalso runs when a push tomainchangesVERSION. It checks the value is semver, tags the merge commitv<VERSION>, and runs goreleaser in the same job. It has to: a tag pushed withGITHUB_TOKENdoesn't start another workflow run. If the tag already exists, it stops without releasing..github/release-notes/v<VERSION>.mdbecomes the release body (via--release-notes). Without it, goreleaser's generated changelog is used, as today.v*tags still release exactly as before.Merging this PR releases nothing, because
VERSIONmatches the existingv0.2.2tag.Tested
actionlintpasses on all three workflows.0.2.2: skipped (tag exists).0.3.0: taggedv0.3.0.0.3.0-rc.1: tagged (goreleaser marks it a pre-release).0.4.0with stray whitespace: taggedv0.4.0.v0.3: rejected.Heads-up
verify-generatedwill show drift here as well. It regenerates from the live catalog, and main is behind it (see #14).🤖 Generated with Claude Code