Busy tab
A busy tab no longer locks up gstack’s browse daemon
When one tab hung, every browse command in gstack failed with daemon busy, and only a force restart got you out, losing your cookies, tabs and logins. Now status checks the daemon itself, and reports the stuck tab separately.
Stuck tab
A stuck tab now says so instead of hanging the command
The tabs list now marks a stuck tab as not responding and moves on. A command that needs that tab times out with an error naming it, and tells you to switch tabs or close it.
Read-only
/cso can verify Rails repairs in a read-only checkout
In a read-only checkout, such as a Nix or Bazel tree, /cso could not write its Rails test config, so no Rails repair got runtime tested. It now replaces those files instead of writing into them.
History
/cso’s Git history stops bringing back a committed .env
/cso keeps .env files and keys out of the tree it reads, but its Git history kept every diff, so a committed .env came back that way. Diffs that touch an excluded file are now withheld.
Verdicts
A failed security check now gets its own verdict
When a repair's security checks fail, /cso now reports assertion failed instead of a misleading incompatible input. A check can also accept several safe rejection codes, like 403 or 404, as long as the secret stays out.
Your turn
The full notes are in gstack’s changelog
CHANGELOG.mdgstack release notes, October 19Both releases are written up in gstack's changelog. Which page has left your browse daemon busy?
