docs: root CHANGELOG.md stops at v0.9.0 — 104 unreleased changesets accumulated #1273

Summary

Root CHANGELOG.md stops at ## [0.9.0] - 2026-03-23. There have been substantial releases since (v0.9.x patches + the entire v0.10 family), shipped via the .changeset/ workflow but never compiled into the root changelog. The .changeset/ folder currently contains 104 unreleased fragment files that have presumably already shipped in published npm packages but never been consolidated.

Evidence

$ grep "^## " CHANGELOG.md
## [Unreleased]
## [0.9.0] - 2026-03-23        ← latest entry
## [0.8.24] - 2026-03-08
## [0.8.23] - 2026-03-12
## [0.8.22] - 2026-03-11
...

$ npm view @bradygaster/squad-cli version
0.10.0   ← latest published, 2026-06-07

$ ls -la .changeset/ | grep -v README | wc -l
103   ← pending fragments

Impact

1. Repo readers can't see what changed in 0.10 — anyone browsing the repo gets a 3-month-stale changelog
2. npm tarball changelogs may or may not exist — I couldn't find packages/squad-cli/CHANGELOG.md or packages/squad-sdk/CHANGELOG.md in the source tree, though changeset publish typically generates them in the tarball
3. squad upgrade users see what? — if the published packages have CHANGELOG.md (per PR chore: include CHANGELOG.md in published npm tarball #1257 which adds them to the files array) they'll get notes; if not, they get nothing
4. docs/.../whatsnew.md is the only place with a partial changelog and it's hand-curated, missing many shipped items

Proposed fixes

1. Run changeset version on the unreleased fragments — generates CHANGELOG.md updates from the fragment files, deletes the fragments. This is the standard Changesets workflow.
2. Consider a CI gate that runs changeset version --dry-run and fails if there are >N fragments older than M days (catches CHANGELOG drift early).
3. Document the release flow so future maintainers know when fragments should be consolidated (today's flow may be that this happens in the release workflow but doesn't commit back to the source tree).

Related

• PR chore: include CHANGELOG.md in published npm tarball #1257 (your PR) adds CHANGELOG.md to the published npm files array — assumes the file is generated; the source-tree gap means it may be the per-package CHANGELOG that gets generated at publish time, not the root one
• Companion issue (filed today): docs: v0.10 feature coverage gap