Skip to content

gstack v1.100.0.0

Latest

Choose a tag to compare

@github-actions github-actions released this 17 Nov 14:10
· 15 commits to main since this release
eff8b78

gstack v1.100.0.0

This release fixes five security advisories in a dependency, makes gstack's shell locks safe on Ubuntu 26.04, and changes how /ship writes and reviews pull requests. One optional hook check is removed.

Fixes

  • Security: hono is pinned to 4.13.16, which fixes five advisories (GHSA-3gg2-335m-rxc6, GHSA-46wx-v44x-9hh2, GHSA-4h7h-rv7c-7m2v, GHSA-4m76-xfj5-7975, GHSA-h7mg-cq63-vhpq) found in 4.13.13. hono reaches gstack only through its development and test tools, and gstack's own code never uses it, so none of the five was reachable; contributors get the fix on their next bun install. (#4408)
  • gstack's shell locks admit exactly one holder again on Ubuntu 26.04 and GitHub's current ubuntu-latest, whose Rust mkdir reports success even when another process created the directory first. Before this, two updates could move one checkout at once, or two gstack-config set calls could drop each other's keys. (#4262)
  • /ship's documentation check no longer wastes one of its two attempts when the checking model writes text after its result line; it is asked once, for free, to resend the result alone. (#4285)
  • Once any result line in that documentation check says "blocked", no later line and no resent answer can turn it into a pass. One gap remains: a blocker written only in plain text after a passing result line still depends on the resent answer reporting it. (#4434)
  • A skill you wrote whose contract still lists check_after_last_edit keeps its other checks. The optional Stop hook skips only that item and prints a SKILL_CONTRACT_SKIPPED line naming the file until you delete it; a contract that lists nothing else is checked for nothing. (#4439)
  • gstack-pr-wait, gstack-ci-gate and the stable release no longer call a commit green when an earlier attempt of a check failed and a rerun created no jobs, or when a workflow failed before starting any job. A failed commit status also counts as red. (#4257)
  • /ship gives the version of a pull request that merges a full review. An earlier review no longer counts once the lines a branch removes have changed with its base, and a PR body's review history keeps every /ship run instead of only the last. (#4365)
  • /ship's test step no longer fails with E2BIG: argument list too long before any test runs on Linux in projects with thousands of unit test files; the files are split across several runner processes and counted as one run. (#4426)
  • /ship's remote test command no longer puts every selected test file on one command line, which Linux refuses past 128 KiB. (#4429)
  • /autoplan's approval page sends a plan back for review when both reviewers challenge it and disagree on whether it is a scope or an order change, asks a plan with no ### Owner's words section to confirm its direction in that case too, and checks an owner quote only against this repository's approvals record. (#4441)
  • /ship accepts a documentation fix when the check named the file with a line number, such as notes.md:8 or notes.md:8:12. (#4437)
  • Ubicloud runs started together can no longer go past the project's vCPU limit, a new ubi-runner.sh room command says how many more VMs fit, and two owners whose ids share a prefix no longer delete each other's expired VMs. (#4430)
  • The daily stable release no longer stalls when gstack's nightly Windows test run fails or doesn't finish. (#4400)
  • The nightly Windows test run finishes within its time limit again, split across eight shards with up-to-date timings. (#4409)
  • The Windows setup test now runs when a pull request changes only bin/gstack-lock.sh. (#4433)
  • The /review test-coverage evaluation no longer fails a run that read the source file when zsh stops at an unquoted echo ====. (#4364)
  • Sixteen documentation links in docs/skills.md and docs/review-policy.md reach their section again. Contributed by @Davmunrey. (#4394)
  • The README links the two new guides, and the install and uninstall docs count and name setup's hooks correctly. (#4403)
  • docs/releases.md says the stable release treats a failed commit status as red and a pending one as still running. (#4436)

Changes

  • Pull requests opened by /ship show at most three plain lines before collapsed sections, and every merge with gstack-ship-queue land lands as one commit titled with the PR title. A repository's .gstack/plain-titles.json can now set body_since (older PRs only get warnings) and extend or replace gstack's default list of in-house words. See docs/writing-prs.md. (#4438)
  • /ship counts review rounds per pull request instead of per run, so a PR shipped several times still gets at most two review rounds, and the version that merges always gets a full review. (#4360)
  • /autoplan's approval page shows a reviewer's challenge to a plan's scope, order, direction, cost or packaging as a choice for the owner, recommending the reviewer's change, instead of defaulting to "keep your direction". Plans can quote their owner under ### Owner's words, and app plans can open with a ### Day one table. (#4431)
  • Claude Code's skill list now says when to use each gstack skill, so requests like "review my changes" load /review. The list grows by about 840 tokens per session. (#4387)
  • /ship's test step prints PREGATE: time limit hit when it runs out of time, and --step-timeout <seconds> sets its budget (default one hour). (#4429)
  • Every skill now tells the agent to ask a question once and to open and clean up every file before handing it over. (#4383)
  • Every skill now tells the agent never to print a whole environment, git config or process listing, and to wait on CI with one gstack-pr-wait call instead of a polling loop. (#4382)
  • gstack agents open each status report with three lines, Failed or skipped:, Unverified: and Also changed:, and keep the report under 250 words. (#4273)
  • /captain's docs name the Failed or skipped: and Also changed: lines and say a missing one is asked for in a follow-up, never a reason to reject the report. (#4432)
  • /eval-plan checks four things it used to leave to judgment: a preregistration's decisions and scoring sections, the judge's agreement with hand labels, and three common ways a result can mislead. (#4384)
  • gstack-runaway reports what a thread's cold and empty wakes cost, not only how many there were, and scan --wakes lists each wake. (#4385)
  • The ship policy guide explains how to merge any pull request with gstack-ship-queue land, including in a repository with one maintainer, with a pinned gh pr merge fallback. (#4377)
  • Two new guides: landing a fix in someone else's repository, and running a playtest with real people. (#4380)
  • ETHOS.md ends its "Explain the Number" section with a three-item checklist for write-ups. (#4381)
  • docs/ship-policy.md documents the .gstack/approval-classes.json schema, the gstack-approval-classes commands and how to cite an owner's approval. (#4355)

Removals

  • The optional Stop hook no longer checks that a test ran after the last edit; /verify asks for that in plain words instead. With /verify loaded, Claude Opus 5.5 and GPT-6.1 Sol already did it in 96% and 89% of runs, and the check moved results by -0.5 to +2 points, inside the noise. (#4428)