Files
msd-core/docs/RELEASE-v1.39.0-rc.4.md
Tom Boucher f983c95ffc Release/1.39.0-rc.4 (#2797)
* chore: bump version to 1.39.0 for release

* chore: bump to 1.39.0-rc.1

* chore: bump to 1.39.0-rc.2

* chore: bump to 1.39.0-rc.3

* chore: bump to 1.39.0-rc.4

* docs: add v1.39.0-rc.4 release notes

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

---------

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>
2026-04-27 22:32:14 -04:00

2.4 KiB
Raw Blame History

v1.39.0-rc.4 Release Notes

Pre-release candidate. Published to npm under the next tag.

npx get-shit-done-cc@next

What's in this release

Added

--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.


Fixed

Codex install no longer corrupts ~/.codex/config.toml (#2760)

Four users confirmed the same breakage: the previous installer left ~/.codex/config.toml in a state that Codex rejected on launch, with manual file cleanup as the only workaround.

The installer now:

  • Strips legacy [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.
  • Emits the GSD-managed hook in the shape the user's config already uses: [[hooks.<Event>]] namespaced AoT if any existing hook uses that form, otherwise top-level [[hooks]].
  • Migrates any legacy [hooks.<Event>] (map format) to [[hooks.<Event>]] (array format) during write.
  • Writes atomically via a temp file + renameSync — no partial writes.
  • Validates the post-write bytes with a strict TOML parser that rejects duplicate keys, repeated table headers, trailing bytes after values, and unsupported value types.
  • On any pre-write or write-time failure, restores the pre-install snapshot and aborts with a clear error instead of warn-and-continue.

Installing the pre-release

# 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 get-shit-done-cc@1.39.0-rc.4

What's next

  • Run rc again on the release branch to publish rc.5 if further fixes land before finalization.
  • Run finalize on the release workflow to promote 1.39.0 to latest when the RC is stable.