docs/RELEASE-v1.39.0-rc.6.md
Pre-release candidate. Published to npm under the next tag.
npx get-shit-done-cc@next
rc.6 is a republish of rc.5. No new fixes were rolled in — release/1.39.0
was bumped from 1.39.0-rc.5 to 1.39.0-rc.6 without first being merged with
main, so the branch contents at the time of tag are byte-for-byte equivalent
to rc.5 plus the version-bump commit.
$ git log v1.39.0-rc.5..v1.39.0-rc.6 --pretty='%h %s'
388118d8 chore: bump to 1.39.0-rc.6
If you are already on 1.39.0-rc.5, there is nothing new to install in rc.6.
The expected next step is an rc.7 cut that first merges main into
release/1.39.0 so the eight fixes that landed after rc.5 reach the registry.
Codex hooks migrator correctness hardening (#2809)
Five edge-cases in the [[hooks.<Event>]] → [[hooks.<Event>.hooks]] two-level
nested schema migration path, discovered across five rounds of code review:
| Finding | Fix |
|---|---|
parseHooksBody used a bare regex (/^([\w.]+)\s*=/) that silently dropped hyphenated keys such as status-message and any quoted TOML key | Replaced with parseTomlKey(), the existing full TOML key parser |
buildNestedBlock unconditionally emitted [[hooks.TYPE.hooks]] even when no handler fields were present, producing an entry with type = "command" but no command | Added guard: matcher-only / handler-field-free sections emit only the event-entry block |
legacyMapSections filter used section.path.startsWith('hooks.') without checking the segment count, so three-segment tables like [hooks.SessionStart.hooks] were misclassified as event entries and re-emitted as bogus nested events | Now uses section.segments.length === 2 (same fix previously applied to staleNamespacedAotSections) |
No regression test for quoted event names containing dots — [[hooks."before.tool"]] has a 2-segment path but 3 dot-parts, and a split('.') check would misclassify it | Regression test added; quoted-dot names are correctly treated as a single two-segment namespace |
Handler command path assertion in install tests used a regex (/gsd-check-update\.js/) rather than the exact absolute path | Strengthened to assert.strictEqual with path.join(codexHome, 'hooks', 'gsd-check-update.js') |
--minimal install flag (alias --core-only) (#2762)
Writes only the six core skills needed to run the main workflow loop:
new-project, discuss-phase, plan-phase, execute-phase, help, update.
No gsd-* subagents are installed.
| Mode | Cold-start system-prompt overhead |
|---|---|
| full (default) | ~12k tokens |
| minimal | ~700 tokens |
Useful for local LLMs with 32K–128K context windows. Sonnet 4.6 / Opus 4.7 users don't need it — the full surface is the right default for cloud models.
The install manifest records mode: "minimal" | "full". Run gsd update without
--minimal at any time to expand to the full skill set.
Codex install no longer corrupts ~/.codex/config.toml (#2760)
The installer now:
[agents] (single-bracket) and [[agents]] (sequence) blocks
unconditionally — both are invalid in the current Codex TOML schema, regardless of
whether a GSD marker is present.[[hooks.<Event>]] namespaced AoT if any existing hook uses that form, otherwise
top-level [[hooks]].[hooks.<Event>] (map format) to [[hooks.<Event>]] (array
format) during write.renameSync — no partial writes.# npm
npm install -g get-shit-done-cc@next
# npx (one-shot)
npx get-shit-done-cc@next
To pin to this exact RC:
npm install -g [email protected]
release/1.39.0 after merging main into the release branch,
so the eight fixes that landed after rc.5 (#2828, #2829, #2831, #2832, #2835,
#2836, #2838, #2839) actually reach the registry.finalize on the release workflow to promote 1.39.0 to latest once an RC
with the full main-branch contents is stable.