Repository navigation
ci: release from commit subjects only, without svu - #10
Merged
Merged
Conversation
svu v2 matched feat:, fix: and BREAKING CHANGE: anywhere in the log, bodies included, and Dependabot puts the changelogs of its updates in the body: chore and ci merges released versions, minor ones among them (gogram v0.13.0 and v0.14.5, gocopy v1.1.0, goreset v1.4.0). A feat!: in such a changelog would have tagged v2.0.0 on a v1 module. The version now comes from the subjects since the last tag: feat → minor, fix → patch, type!: → minor while on v0, nothing else releases. A breaking change on v1+ fails the job, as it needs a /vN module path. The release is created on the commit that passed CI, and the workflow is the same in every repository. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
darxnet
enabled auto-merge (squash)
November 13, 2026 13:52
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
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.
svu v2 matched
feat:,fix:andBREAKING CHANGE:anywhere ingit log, commit bodies included. Dependabot squash merges carry the dependency's changelog in the body, so chore and ci merges released versions: gogram v0.13.0 (minor, fromfeat!: node 24 supportin an Actions changelog) and v0.14.5, gocopy v1.1.0, goreset v1.4.0. Afeat!:in such a changelog would have tagged v2.0.0 on a v1 module, which Go cannot use without a/v2path. svu v3 reads feat/fix from titles only but still takesBREAKING CHANGE:from bodies.The release step now computes the version from the Conventional Commit subjects since the last tag:
type!:→ minor while on v0; on v1+ the job fails, since a breaking change needs a/vNmodule path and is released by handfeat→ minor,fix→ patch, anything else → no release--target "$GITHUB_SHA", on the commit that passed CIReplayed over the tag history of all seven repositories, it reproduces every automatic tag except the spurious ones above (and matches svu v3 on all of them).
setup-goand svu are gone from the job, andrelease.ymlis now identical in every repository.