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>
1.1 KiB
type, pr
| type | pr |
|---|---|
| Fixed | 3658 |
gsd-graphify-update.sh now matches gsd-sdk query commit (#3653) — the PostToolUse auto-update hook previously substring-matched only direct shell git ops in tool_input.command. Because gsd-sdk query commit invokes git via spawnSync('git', [...]) rather than through a shell, the literal git commit never appears in the Bash tool's command string, and the hook silently skipped every SDK-issued commit — including the phase.complete-following commit that closes every phase. Result: .planning/graphs/ drifted stale by one or more commits at the end of every phase, with no error and no log. Gate 2 now also accepts the exact gsd-sdk query commit command shape, which is the user-facing invocation that triggers the SDK-internal spawnSync('git', 'commit', ...), without matching sibling verbs such as commit-to-subrepo. Other gsd-sdk query verbs (phase.complete, roadmap.update-plan-progress, state.begin-phase) do not invoke git themselves and remain non-matching to avoid spurious rebuilds per state mutation.