Files
msd-core/.changeset/archived/3621-cherry-pick-test-fixtures.md
Tom Boucher 8616839cab chore: archive 463 shipped changeset fragments before wiring render (#714)
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>
2026-06-05 14:53:17 -04:00

720 B

get-shit-done-cc
get-shit-done-cc
patch

Fixed: hotfix releases now correctly cherry-pick test-fixture updates. The release-sdk.yml auto-cherry-pick loop accepts test: commits (in addition to fix: and chore:), and the shipped-paths classifier treats tests/<name> and sdk/src/<name>/<file>.test.<ts|cjs|mjs|js> as CI-gating-equivalent. When a production fix is bundled with a fix: commit but the matching test-fixture alignment lands in a separate test: commit, both are now picked together — preventing the CI-red state that broke the v1.42.3 hotfix attempt. The .github/workflows/<file> push-blocking guard is preserved (#2980): bundles touching workflow files still skip regardless of other content.