Skip to content

ci: release from commit subjects only, without svu - #10

Merged
darxnet merged 1 commit into
mainfrom
ci/release-from-subjects
Nov 13, 2026
Merged

darxnet merged 1 commit into
mainfrom
ci/release-from-subjects

Conversation

@darxnet

@darxnet darxnet commented Nov 13, 2026

Copy link
Copy Markdown
Owner

svu v2 matched feat:, fix: and BREAKING CHANGE: anywhere in git 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, from feat!: node 24 support in an Actions changelog) 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, which Go cannot use without a /v2 path. svu v3 reads feat/fix from titles only but still takes BREAKING 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 /vN module path and is released by hand
  • feat → minor, fix → patch, anything else → no release
  • no tag yet → no release (the first tag is made by hand)
  • the release is created with --target "$GITHUB_SHA", on the commit that passed CI

Replayed 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-go and svu are gone from the job, and release.yml is now identical in every repository.

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
darxnet enabled auto-merge (squash) November 13, 2026 13:52
@codecov

codecov Bot commented Nov 13, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

@darxnet
darxnet merged commit 2132db0 into main Nov 13, 2026
9 checks passed
@darxnet
darxnet deleted the ci/release-from-subjects branch November 13, 2026 13:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant