Repository navigation
v3.0.1
What's new
A follow-up patch to the v3.0.0 major release — hardening the release-notes tooling that shipped in v3.0.0 and finishing the post-tag schema cleanup that could only happen once the v3 tag existed.
Bug Fixes
The release-notes-narrative skill's step-13 rollback gate previously asserted that a rewritten narrative body must be longer than the auto-generated body it replaced. That assumption broke on major releases: the v3.0.0 squash commit embedded its entire prose under BREAKING CHANGES in the auto-generated body (11,048 chars), so the correctly-rendered 4,394-char narrative was auto-rolled back by CI — the length gate rejected exactly the rewrite it was meant to protect (#644).
Step 13 now verifies the render contract structurally instead: the body must start with ## What's new, contain at least one recognized bucket heading, include the Compare link, and differ from the pre-edit snapshot. Length comparison is explicitly forbidden, with the v3.0.0 incident recorded as the rationale.
Miscellaneous Chores
With the v3 tag now cut, the schema publishing pipeline moved off its v2-transition scaffolding. The published schema is now regenerated at docs/public/schemas/v3/ (byte-identical to latest/, with $id pointing at the v3 URL), and the tracked v2/ bridge copy was deleted. The release-gated v2-mirror cleanup step was removed from docs.yaml since the real directory deletion now supersedes that transition hack, and the configuration reference was regenerated so $schema examples cite v3 (including a hand-written v2 URL fix in the Schema and Autocomplete section). schema:drift now reports "up to date (v3)"; the docs build is green, all 85 schema tests pass, and typecheck/lint/content-integrity are clean (#643).
Also in this release
- deps: update all non-major dependencies (#642)