CHANGELOG promotion was a manual operator step that was never run, so 463 fragments for work already shipped in <=1.3.1 accumulated in .changeset/. Their notes were already hand-curated into the dated [1.2.0]/[1.3.0]/[1.3.1] CHANGELOG sections (#690 backfill, PR #694). Rendering them now would duplicate and mis-attribute shipped work. Move them to .changeset/archived/ (read non-recursively by all changeset tooling, so never rendered), keeping only the 3 genuinely-unreleased fragments at the top level. Prep for wiring `render` into the release finalize job (#690 follow-up). Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
647 B
647 B
type, pr
| type | pr |
|---|---|
| Added | 2975 |
Changeset-fragment workflow — eliminates CHANGELOG.md merge conflicts. Each PR drops .changeset/<random-name>.md with frontmatter (type:, pr:) plus a markdown body; the release-time npm run changelog:render consolidates fragments into CHANGELOG.md and deletes them. CI lint (npm run lint:changeset) requires a fragment on any PR touching user-facing files (bin/, get-shit-done/, agents/, commands/, hooks/, sdk/src/); contributors can opt out via the no-changelog label for purely internal changes. See .changeset/README.md and CONTRIBUTING.md for the workflow.