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>
866 B
866 B
type, pr
| type | pr |
|---|---|
| Fixed | 3573 |
Codex installer now emits canonical [features].hooks on fresh inserts (no longer writes deprecated codex_hooks) — Codex's own source marks codex_hooks as a legacy_key (codex-rs/features/src/legacy.rs). The GSD installer was writing the deprecated key on every install / reinstall on Codex CLI ≥ 0.130.0. The installer now writes the canonical [features].hooks = true (section, root-dotted, and block-fallback forms) and the runtime check recognizes both hooks and legacy codex_hooks as enabling the feature. Pre-existing legacy lines (user-authored or from older GSD installs) are preserved untouched — Codex's own legacy_key alias handles them at the runtime layer, so there's no breaking change for existing configs. Closes #3566.