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>
616 B
616 B
type, pr
| type | pr |
|---|---|
| Fixed | 3767 |
verify-reapply-patches no longer false-fails when gsd-pristine/ has been refreshed to a newer version — the verifier now reads pristine_hashes from backup-meta.json and validates each on-disk pristine file's SHA-256 before using it as a diff baseline; when a mismatch is detected (indicating the snapshot was overwritten by a later GSD update after the backup was captured), the file is reported as ok with reason ok_pristine_drift_detected rather than producing spurious fail_user_lines_missing failures for every line the upstream removed between the two versions.