ci: add release-please and conventional-commit PR title enforcement - #63
Merged
Conversation
Conventional commits on main accumulate into a release-please PR that bumps pixi.toml's version and CHANGELOG.md; merging it tags the release. PR titles are linted (squash-merge makes them the commits release-please reads). bootstrap-sha anchors at current main so only future commits count toward the next release. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This was referenced Aug 14, 2026
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.
Summary
Sets up automated releases, analogous to fibertools-rs (which uses the Rust-specific release-plz; FIRE uses release-please since it is not a cargo project):
main: conventional commits accumulate into a release PR that bumpsversioninpixi.toml(via TOML jsonpath) and updatesCHANGELOG.md; merging that PR tagsvX.Y.Zand cuts a GitHub release.bootstrap-shaanchors at the current main head, so only commits merged after this PR count toward the next release.feat:(minor bump) changes FIRE's-vX.Y-output directory names whilefix:(patch) does not.Versioning:
bump-minor-pre-majoris set, so while pre-1.0,feat:and breaking changes bump the minor version andfix:bumps the patch — matching the intent of fibertools-rs's release-plz config.Interaction with #62
Intended to merge before #62. When #62 is then squash-merged with a
feat:title, release-please will propose exactly0.2.0(manifest 0.1.2 + feat). #62 already bumpspixi.tomlto 0.2.0 and hand-writes the v0.2.0 changelog entry, so the first release PR will be reconciled by hand once (keep the richer hand-written entry) — after that, everything is automatic.