Skip to content

docs: state the weekly limit on stable-export changes (WC-REL-9) - #1659

Merged
leemour merged 2 commits into
mainfrom
docs/wc-rel-9-weekly
Oct 19, 2026
Merged

leemour merged 2 commits into
mainfrom
docs/wc-rel-9-weekly

Conversation

@leemour

@leemour leemour commented Oct 19, 2026 •

Copy link
Copy Markdown
Collaborator

Handbook rule WC-REL-9 (reworded in WireCatLabs/cli-base#265) limits a change to a stable export that makes a CLI change its code to one release a week. docs/REFERENCE.md said such a change "is not held back for a special release", and both REFERENCE.md and CLAUDE.md said there is no gap between releases, which conflicts.

  • docs/REFERENCE.md, "How often, and what may break": states WC-REL-9 in plain words with a link. A change to a stable export counts unless all three parity jobs (tg-cli, max-cli, whatsapp-cli) pass with each CLI's main unchanged; it also counts when it passes only against a CLI branch made for it, or compiles but changes behaviour a CLI must adapt to; when in doubt, it counts. Those changes go into one release a week, and every CLI moves to it the same day. The "not held back" clause and "CLIs pace their own" go; "no gap" now excepts the weekly limit.
  • CLAUDE.md constraint 5: the same rule in one line with the link; "no fixed gap" excepts the weekly limit.

Docs only, no changelog line, no impact on callers. pnpm docs:check passes.

🤖 Generated with Claude Code

Co-Authored-By: Claude Opus 5.5 (1M context) noreply@anthropic.com

leemour and others added 2 commits October 19, 2026 14:01
The API reference said a change to a stable export "is not held back for a
special release", which conflicts with the handbook rule WC-REL-9: a change
to a stable export that makes a CLI change its code ships at most once a
week. It does not count only when all three parity jobs pass with each
CLI's main unchanged; when in doubt, it counts.

"How often, and what may break" now states that rule and links it, and
the CLAUDE.md summary repeats it in one line. "Release when a consumer
needs it" stays: it still holds for every other change.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
REFERENCE.md now says a change also counts when it passes only against a CLI
branch made for it. The "no gap between releases" lines in REFERENCE.md and
CLAUDE.md now except the weekly limit, and the "CLIs pace their own" clause
goes, since WC-REL-9 moves every CLI on the same day.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
@leemour
leemour merged commit 3f6c374 into main Oct 19, 2026
13 checks passed
@leemour leemour mentioned this pull request Oct 19, 2026
leemour added a commit that referenced this pull request Oct 19, 2026
Release 0.363.0 from main 95234d9: #1660 (evidence findings, additive),
#1657 and #1659 (docs). Only package.json and the CHANGELOG heading
change.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-authored-by: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant