gstack 1.91.13.0 runs /autoplan again and stops merging over red CI

1 week ago

What changed in gstack 1.91.13.0: /autoplan runs again in sessions with SessionStart hooks, /land-and-deploy no longer merges over red CI, projects in nested Git groups get their own saved state, never-ask preferences now fire, and three more fixes. https://github.com/garrytan/gstack/blob/main/CHANGELOG.md#191130---2026-10-02

Ask

Ask about this presentation

Answers are generated from this presentation.

Chapters

  1. 0:00/autoplan runs with SessionStart hooks
  2. 0:15/land-and-deploy waits for every check
  3. 0:28Nested-group projects get their own state
  4. 0:43Never-ask preferences now fire
  5. 0:55Three more fixes
Show transcript

/autoplan runs with SessionStart hooks

gstack logo

gstack 1.91.13.0 runs /autoplan again in sessions with SessionStart hooks

after /compact and /clearforked resumeWindows paths
Unrecognized but healthy session: a warning, then it continues
01 /autoplan02 Deploy03 Projects04 Preferences05 Fixes
garrytan/gstack · CHANGELOG.md

In gstack 1.91.13.0, /autoplan runs again once a plugin installs a SessionStart hook. Its guard had blocked every phase. It also works after compact, clear, a forked resume, and on Windows.

/land-and-deploy waits for every check

/land-and-deploy no longer merges over red CI

BEFORE
no required checks → merge

Without branch protection, it could merge while CI was red or still running.

NOW
every check on the merged commit

Red, pending or missing CI needs your approval for that commit.

01 /autoplan02 Deploy03 Projects04 Preferences05 Fixes
garrytan/gstack · CHANGELOG.md

/land-and-deploy no longer merges over failing CI. Without branch protection, as on every private repo on GitHub Free, it could merge while checks were red. Now it waits for every check, or asks you.

Nested-group projects get their own state

Projects in nested Git groups stop sharing saved state

BEFORE
group/subgroup/repo → one bucket

/context-restore could offer another project's checkpoint.

NOW
projects/<repo>-<hash>/

GitLab subgroups, Azure DevOps, Bitbucket Server

GitHub buckets do not move. The old shared bucket stays in place.
01 /autoplan02 Deploy03 Projects04 Preferences05 Fixes
garrytan/gstack · CHANGELOG.md

Projects on GitLab subgroups, Azure DevOps or Bitbucket Server now keep their own saved state, so /context-restore stops offering another project's checkpoint. GitHub projects stay put, and the old shared folder is left in place.

Never-ask preferences now fire

Questions you set to never-ask now decide on their own

never-ask, set in /plan-tuneauto-decides
one-way questionsalways ask, CI approvals included
01 /autoplan02 Deploy03 Projects04 Preferences05 Fixes
garrytan/gstack · CHANGELOG.md

Questions you tuned to never ask in /plan-tune now decide on their own. The hook had read the wrong project identity. One-way questions, including the new CI approvals, still ask.

Three more fixes

Brain context, the /codex gate and SARIF imports work again

brain contextLoads in every skill, after loading 0 bytes
/codexA clean Codex review can pass the gate
/cso import-sarifKeeps semgrep and trivy results
CHANGELOG.mdEvery fix in 1.91.13.0
01 /autoplan02 Deploy03 Projects04 Preferences05 Fixes
garrytan/gstack · CHANGELOG.md

Brain context loads again in every skill, after loading nothing. A clean Codex review can now pass the /codex gate. And /cso keeps semgrep and trivy results when it imports SARIF. The changelog lists the rest.