chore(main): release 0.9.0 - #196
Merged
krakennetworks merged 14 commits intoAug 20, 2026
Merged
Conversation
se-jo-ma
pushed a commit
that referenced
this pull request
Aug 20, 2026
The `focus_order` fix in #195 carried a `BREAKING CHANGE:` footer, and release-please's default for a 0.x project is to treat that as the signal to cut 1.0.0 -- so PR #196 opened as "chore(main): release 1.0.0". Nothing about that branch was a decision to declare the API stable. `bump-minor-pre-major` makes a breaking change bump the minor while the project is on 0.x, which is what SemVer allows pre-1.0 and what VERSIONING.md now documents. `bump-patch-for-minor-pre-major` stays off: a feature should still move the minor, not hide in a patch. 1.0.0 becomes a deliberate act -- a commit that raises the version explicitly, after the readiness audit -- rather than a side effect of a commit footer. Signed-off-by: Sean Mauk <seanmauk@krakennetworks.com>
se-jo-ma
pushed a commit
that referenced
this pull request
Aug 20, 2026
The `focus_order` fix in #195 carried a `BREAKING CHANGE:` footer, and release-please's default for a 0.x project is to treat that as the signal to cut 1.0.0 -- so PR #196 opened as "chore(main): release 1.0.0". Nothing about that branch was a decision to declare the API stable. `bump-minor-pre-major` makes a breaking change bump the minor while the project is on 0.x, which is what SemVer allows pre-1.0 and what VERSIONING.md now documents. `bump-patch-for-minor-pre-major` stays off: a feature should still move the minor, not hide in a patch. 1.0.0 becomes a deliberate act -- a commit that raises the version explicitly, after the readiness audit -- rather than a side effect of a commit footer. Signed-off-by: Sean Mauk <seanmauk@krakennetworks.com>
krakennetworks
approved these changes
Aug 20, 2026
release-please runs with skip-changelog, so CHANGELOG.md is hand-curated and the release PR does not write it. check_version_sync.py compares the newest release heading against pyproject.toml, so the 0.9.0 release PR fails the required docs job until the entry exists. docs/changelog.json is regenerated from the new entry. Signed-off-by: Sean Mauk <mauk.sean@gmail.com>
….noreply.github.com> On behalf of release-bot <release-bot@users.noreply.github.com>, I, Sean Mauk <mauk.sean@gmail.com>, hereby add my Signed-off-by to this commit: 8a7e38f On behalf of release-bot <release-bot@users.noreply.github.com>, I, Sean Mauk <mauk.sean@gmail.com>, hereby add my Signed-off-by to this commit: 8a91089 Signed-off-by: Sean Mauk <mauk.sean@gmail.com>
krakennetworks
deleted the
release-please--branches--main--components--fathom-rules
branch
August 20, 2026 14:21
Member
Author
|
🤖 Created releases: 🌻 |
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
3 participants
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.
🤖 I have created a release beep boop
0.9.0 (2026-08-20)
⚠ BREAKING CHANGES
focus_orderis now the execution order it always claimed to be. A multi-module ruleset relying on the previous inverted behaviour must reverse itsfocus_orderlist. Single-module rulesets are unaffected, as are rulesets whose modules do not write competing decisions.Bug Fixes
Documentation
This PR was generated with Release Please. See documentation.