docs(ci): the bump-level rule — an additive widening of a published surface is at least minor (ruling C, #15294) - #15380
Merged
Conversation
…urface is at least minor Record the maintainer's ruling (2026-09-04, decision batch #35) where authors already read the changeset rules: the `Check Changeset` step's route-1 prose in `.github/workflows/pr-automation.yml`, plus a one-line cross-reference from the header of `scripts/check-changeset-no-major.mjs`, which already carries the launch-window reasoning the rule's last sentence depends on. Prose only: no new gate, no behaviour change, nothing retro-fixed. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_012zGPuVVX3deAx9LdjK8jCk
claude
Bot
added
the
skip-changeset
baozhoutao
marked this pull request as ready for review
September 4, 2026 13:36
baozhoutao
enabled auto-merge
September 4, 2026 13:36
baozhoutao
deleted the
claude/issue-15294-additive-widening-bump-rule
branch
September 4, 2026 14:22
This was referenced Sep 4, 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
2 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.
Fixes #15294
Records maintainer ruling C as prose, in the two places the issue named. No new gate, no behaviour change, nothing retro-fixed.
Provenance
Ruling C, recorded on #15294 as comment 5540571415 by the Director seat: "Provenance: maintainer, live PM chat, 2026-09-04, decision batch #35, verbatim 「同意」 on the presented recommendation
1A · 2(Q1 A · Q2 A · Q3 B→A)(this card is item 3, C)." Ruling authority: maintainer 2026-09-04 (batch #35).Where the paragraph now appears
.github/workflows/pr-automation.yml— inside theRequire a changeset (or the skip-changeset label)step of theCheck Changesetjob, in the heredoc the step prints to the job log when a PR adds no changeset. It sits under route 1 ("It releases something -> run 'pnpm changeset' and name the packages it releases"), because route 1 is exactly the moment an author has to pick a level. It opensWHICH LEVEL:and carries the ruled sentence, then its provenance, then the two things the ruling explicitly rules out (the 64 historicalpatchprecedents are pre-rule; this is prose, not a gate).scripts/check-changeset-no-major.mjs— a cross-reference in the file header, placed immediately after the paragraph that explains why the bump level is not the carrier of breaking-ness during the launch window, since that is the sentence the rule's last clause depends on. It states the floor in one line and points at the workflow prose and at finding(changeset): two independent contract reviews read the repo's own history to opposite bumps for "add an exported symbol to a published index" #15294 for the full text.The ruled sentence is reproduced word for word; only the markdown bold markers around its first sentence were dropped, because the destination is a plain-text job log rather than rendered markdown.
Verification
Every run below was made on the branch head
fad832b7e(git rev-parse --short HEAD), the final commit of this PR.runscript was extracted with a YAML parser fromHEAD~1and fromHEAD: with the heredoc body excluded the two shell scripts are byte-identical, and executing both underADDED=0,ADDED=2andADDED=n/agives the same exit codes on both (1,0,0).git diff -U0 -- scripts/check-changeset-no-major.mjsfiltered to lines that are not block-comment continuations is empty (0 lines), so the floor, the roster and the--self-testfixtures are untouched;check-changeset-no-major.mjs --self-testis green.scripts/pm/dispatch-gates.mjs --commands --repo objectstack-ai/objectstack) is green, plus the always-runs tail and the roster families whose lists live under the two touched directories. Whole-repopnpm lint(eslint . --no-inline-config) is green with zero findings, run in the foreground under the shared verify lock (os-verify-lock: VERDICT command-exit 0). Full accounting in the report comment on finding(changeset): two independent contract reviews read the repo's own history to opposite bumps for "add an exported symbol to a published index" #15294.skip-changeset: this PR releases nothing — a workflow comment/prose change plus a comment line in a repo script.🤖 Generated with Claude Code
https://claude.ai/code/session_012zGPuVVX3deAx9LdjK8jCk
Generated by Claude Code