feat(release): derive versions from commit history - #76
Merged
Conversation
danielkov
force-pushed
the
feat/automatic-release-versioning
branch
from
September 1, 2026 15:01
905a0e7 to
8b0a3ed
Compare
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.
Summary
Derive each release version from Conventional Commit history since the latest published release. The release workflow now prepares one versioned candidate, builds every artifact from it, and atomically advances
maintogether with the release tag.Motivation
Per-PR version bumps conflict across parallel workstreams and assign a separate version to every merged change. This groups all non-breaking changes into one patch release while promoting any
!orBREAKING CHANGE:commit to a minor release.Impact
Ordinary pull requests must stop editing release versions and use Conventional Commit titles. Merge this PR only after the final manually versioned release tag matches
Cargo.toml.Technical details
Version selection
A dependency-free calculator validates landed commit subjects, applies one patch bump by default, and lets a breaking commit select a minor bump. CI exercises patch, bang, body-footer, invalid-history, and invalid-range cases, while the required
testjob validates PR titles.Release candidate
The workflow updates
Cargo.tomlandCargo.lockin an unpushed release commit and transports that commit to Linux, macOS, release-note, and container jobs with an incremental Git bundle. After all required builds succeed, a leased atomic push advancesmainand creates the tag together; failed publication can resume from the existing release commit.