8616839cab
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>
945 B
type, pr
| type | pr |
|---|---|
| Fixed | 3346 |
Codex AoT hooks migration uses event-name leaf key, not location tuple — migrateCodexHooksMapFormat in bin/install.js re-emitted the legacy [hooks.<X>] section's path segment verbatim as the leaf TOML key of the new [[hooks.<EVENT>]] two-level nested AoT block. When the legacy table key was a <file>:<event>:<line>:<col> location identifier (with the actual event name in an event = "..." body field), the migration produced a header like [[hooks."C:\Users\helen\.codex\config.toml:session_start:0:0"]], which Codex 0.124.0+ refuses to load. The map-format and stale-namespaced-AoT branches now mirror the flat-AoT branch: when the section body declares event = "...", that name wins as the leaf key (and event is excluded from the re-emitted handler body). npx get-shit-done-cc@latest no longer aborts the Codex runtime install on Windows configs that pre-date the AoT migration. (#3346)