Repository navigation
fix(inkless:release): exclude sync-tooling commits from the branch-consistency gate - #794
Merged
Merged
Conversation
…nsistency gate branch-consistency.sh --check is the release gate: the release workflow runs it per active branch and refuses to tag while any actionable main commit is missing. The check matches by PR number and only excluded titles starting with sync(, fix(sync), docs(sync), or refactor(sync). Sync-tooling PRs use the scopes inkless-sync, inkless:sync, and inkless:release-sync, so they did not match and the gate counted them as missing on every release branch. They only touch inkless-sync/, which no release branch reads: the sync guides copy main's inkless-sync/ into the sync worktree. Since 0.47 that covered #768, #770, #776, and #780 on inkless-4.1 and inkless-4.2, and #780 on inkless-4.3. Match any conventional-commit type with those scopes, in addition to the existing sync( prefix. inkless:ci and inkless:release commits keep counting: they change workflows, build files, and docs that release branches do carry. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
jeqo
marked this pull request as ready for review
September 9, 2026 09:03
tvainika
approved these changes
Sep 9, 2026
jeqo
added a commit
that referenced
this pull request
Sep 9, 2026
…nsistency gate (#794) branch-consistency.sh --check is the release gate: the release workflow runs it per active branch and refuses to tag while any actionable main commit is missing. The check matches by PR number and only excluded titles starting with sync(, fix(sync), docs(sync), or refactor(sync). Sync-tooling PRs use the scopes inkless-sync, inkless:sync, and inkless:release-sync, so they did not match and the gate counted them as missing on every release branch. They only touch inkless-sync/, which no release branch reads: the sync guides copy main's inkless-sync/ into the sync worktree. Since 0.47 that covered #768, #770, #776, and #780 on inkless-4.1 and inkless-4.2, and #780 on inkless-4.3. Match any conventional-commit type with those scopes, in addition to the existing sync( prefix. inkless:ci and inkless:release commits keep counting: they change workflows, build files, and docs that release branches do carry. Co-authored-by: Claude Fable 5.1 <noreply@anthropic.com>
jeqo
added a commit
that referenced
this pull request
Sep 9, 2026
…nsistency gate (#794) branch-consistency.sh --check is the release gate: the release workflow runs it per active branch and refuses to tag while any actionable main commit is missing. The check matches by PR number and only excluded titles starting with sync(, fix(sync), docs(sync), or refactor(sync). Sync-tooling PRs use the scopes inkless-sync, inkless:sync, and inkless:release-sync, so they did not match and the gate counted them as missing on every release branch. They only touch inkless-sync/, which no release branch reads: the sync guides copy main's inkless-sync/ into the sync worktree. Since 0.47 that covered #768, #770, #776, and #780 on inkless-4.1 and inkless-4.2, and #780 on inkless-4.3. Match any conventional-commit type with those scopes, in addition to the existing sync( prefix. inkless:ci and inkless:release commits keep counting: they change workflows, build files, and docs that release branches do carry. Co-authored-by: Claude Fable 5.1 <noreply@anthropic.com>
jeqo
added a commit
that referenced
this pull request
Sep 9, 2026
…nsistency gate (#794) branch-consistency.sh --check is the release gate: the release workflow runs it per active branch and refuses to tag while any actionable main commit is missing. The check matches by PR number and only excluded titles starting with sync(, fix(sync), docs(sync), or refactor(sync). Sync-tooling PRs use the scopes inkless-sync, inkless:sync, and inkless:release-sync, so they did not match and the gate counted them as missing on every release branch. They only touch inkless-sync/, which no release branch reads: the sync guides copy main's inkless-sync/ into the sync worktree. Since 0.47 that covered #768, #770, #776, and #780 on inkless-4.1 and inkless-4.2, and #780 on inkless-4.3. Match any conventional-commit type with those scopes, in addition to the existing sync( prefix. inkless:ci and inkless:release commits keep counting: they change workflows, build files, and docs that release branches do carry. Co-authored-by: Claude Fable 5.1 <noreply@anthropic.com>
jeqo
added a commit
that referenced
this pull request
Sep 10, 2026
* docs(inkless:sync): archive the 0.48 cherry-pick sessions for 4.1, 4.2, 4.3 Session logs for bringing the three active release branches up to main (5fa6669, #784) ahead of the 0.48 release. inkless-4.3 took its 8 commits clean. inkless-4.2 and inkless-4.1 took 19 each; the logs record the conflict resolutions and the sync(compile)/sync(test) adaptations needed for the 4.2.1 and 4.1.2 APIs (Record package, LogReadResult constructor, Seq-based DelayedFetch statuses). Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> docs(inkless:sync): complete the 0.48 cherry-pick session logs The three branches took six more main commits (#794, #787, #792, #793, tables and the verification that covered them. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> * docs(inkless:release): list inkless-4.3 as an active release branch inkless-4.3 is on Kafka 4.3.1 (#779) and gets its first Kafka-base tag with 0.48, so it moves from Planned to Active in RELEASES.md. The release workflow header names it among the branches the cherry-pick sync has to cover before a run. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> * docs(inkless:release): add 0.48 changelog entry Generated from inkless-release-0.47..inkless-release-0.48 and curated: every metric delta traced to its commit, the four config default changes the configs.rst diff shows added next to the four new keys, and the V28 lock on logs described for operators. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> --------- Co-authored-by: Claude Fable 5.1 <noreply@anthropic.com>
giuseppelillo
pushed a commit
that referenced
this pull request
Sep 18, 2026
* docs(inkless:sync): archive the 0.48 cherry-pick sessions for 4.1, 4.2, 4.3 Session logs for bringing the three active release branches up to main (5fa6669, #784) ahead of the 0.48 release. inkless-4.3 took its 8 commits clean. inkless-4.2 and inkless-4.1 took 19 each; the logs record the conflict resolutions and the sync(compile)/sync(test) adaptations needed for the 4.2.1 and 4.1.2 APIs (Record package, LogReadResult constructor, Seq-based DelayedFetch statuses). Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> docs(inkless:sync): complete the 0.48 cherry-pick session logs The three branches took six more main commits (#794, #787, #792, #793, tables and the verification that covered them. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> * docs(inkless:release): list inkless-4.3 as an active release branch inkless-4.3 is on Kafka 4.3.1 (#779) and gets its first Kafka-base tag with 0.48, so it moves from Planned to Active in RELEASES.md. The release workflow header names it among the branches the cherry-pick sync has to cover before a run. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> * docs(inkless:release): add 0.48 changelog entry Generated from inkless-release-0.47..inkless-release-0.48 and curated: every metric delta traced to its commit, the four config default changes the configs.rst diff shows added next to the four new keys, and the V28 lock on logs described for operators. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> --------- Co-authored-by: Claude Fable 5.1 <noreply@anthropic.com>
giuseppelillo
pushed a commit
that referenced
this pull request
Sep 18, 2026
* docs(inkless:sync): archive the 0.48 cherry-pick sessions for 4.1, 4.2, 4.3 Session logs for bringing the three active release branches up to main (5fa6669, #784) ahead of the 0.48 release. inkless-4.3 took its 8 commits clean. inkless-4.2 and inkless-4.1 took 19 each; the logs record the conflict resolutions and the sync(compile)/sync(test) adaptations needed for the 4.2.1 and 4.1.2 APIs (Record package, LogReadResult constructor, Seq-based DelayedFetch statuses). Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> docs(inkless:sync): complete the 0.48 cherry-pick session logs The three branches took six more main commits (#794, #787, #792, #793, tables and the verification that covered them. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> * docs(inkless:release): list inkless-4.3 as an active release branch inkless-4.3 is on Kafka 4.3.1 (#779) and gets its first Kafka-base tag with 0.48, so it moves from Planned to Active in RELEASES.md. The release workflow header names it among the branches the cherry-pick sync has to cover before a run. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> * docs(inkless:release): add 0.48 changelog entry Generated from inkless-release-0.47..inkless-release-0.48 and curated: every metric delta traced to its commit, the four config default changes the configs.rst diff shows added next to the four new keys, and the V28 lock on logs described for operators. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> --------- Co-authored-by: Claude Fable 5.1 <noreply@anthropic.com>
giuseppelillo
pushed a commit
that referenced
this pull request
Sep 24, 2026
* docs(inkless:sync): archive the 0.48 cherry-pick sessions for 4.1, 4.2, 4.3 Session logs for bringing the three active release branches up to main (5fa6669, #784) ahead of the 0.48 release. inkless-4.3 took its 8 commits clean. inkless-4.2 and inkless-4.1 took 19 each; the logs record the conflict resolutions and the sync(compile)/sync(test) adaptations needed for the 4.2.1 and 4.1.2 APIs (Record package, LogReadResult constructor, Seq-based DelayedFetch statuses). Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> docs(inkless:sync): complete the 0.48 cherry-pick session logs The three branches took six more main commits (#794, #787, #792, #793, tables and the verification that covered them. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> * docs(inkless:release): list inkless-4.3 as an active release branch inkless-4.3 is on Kafka 4.3.1 (#779) and gets its first Kafka-base tag with 0.48, so it moves from Planned to Active in RELEASES.md. The release workflow header names it among the branches the cherry-pick sync has to cover before a run. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> * docs(inkless:release): add 0.48 changelog entry Generated from inkless-release-0.47..inkless-release-0.48 and curated: every metric delta traced to its commit, the four config default changes the configs.rst diff shows added next to the four new keys, and the V28 lock on logs described for operators. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> --------- Co-authored-by: Claude Fable 5.1 <noreply@anthropic.com>
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.
branch-consistency.sh --check is the release gate: the release workflow runs it per active branch and refuses to tag while any actionable main commit is missing. The check matches by PR number and only excluded titles starting with sync(, fix(sync), docs(sync), or refactor(sync).
Sync-tooling PRs use the scopes inkless-sync, inkless:sync, and inkless:release-sync, so they did not match and the gate counted them as missing on every release branch. They only touch inkless-sync/, which no release branch reads: the sync guides copy main's inkless-sync/ into the sync worktree. Since 0.47 that covered #768, #770, #776, and #780 on inkless-4.1 and inkless-4.2, and #780 on inkless-4.3.
Match any conventional-commit type with those scopes, in addition to the existing sync( prefix. inkless:ci and inkless:release commits keep counting: they change workflows, build files, and docs that release branches do carry.