Skip to content

Commit 75fc1c3

Browse files
committed
chore(changeset): grade @objectstack/cli minor under the clause-② ruling
The PM ruled clause-② `yes` on card #16600: copying this command's existing `{ error, ... }` envelope onto a path that could not reach it is the widening branch triage enumerated. `check-changeset-no-major`'s way 1 then applies — the declaration is right and the level was wrong. Records why no BREAKING banner rides with it. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01YFY46JydE1gMxQG1TqBcMZ
1 parent cba32a4 commit 75fc1c3

1 file changed

Lines changed: 3 additions & 1 deletion

File tree

.changeset/i18n-extract-check-json-compares.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
"@objectstack/cli": patch
2+
"@objectstack/cli": minor
33
---
44

55
`os i18n extract --check --json` now COMPARES. It used to exit 0 having compared nothing, on a tree whose bundles had provably drifted.
@@ -16,3 +16,5 @@ What each invocation now does, with no new member on any published payload:
1616
- **`--json` without `--check`** — unchanged in every respect.
1717

1818
The run leaves through exactly one of those faces, so stdout still parses as exactly one JSON document.
19+
20+
Graded `minor` rather than `patch` because the PM's clause-② ruling on this card reads the reuse of the existing envelope on a newly reachable path as a widening of the published output face; the maintainer's 2026-09-04 rule puts an already-declared widening at `minor` at least. Nothing an author can write is removed, renamed or narrowed here, and the failure prescribes no consumer code change — so no `**BREAKING**` banner and no ADR-0087 disposition ride along.

0 commit comments

Comments
 (0)