Repository navigation
0.10.1 - six things that were silently broken for every user
tower setup --url ... --token ... wrote your team token into a file teams commit.
0.10.0 moved the token out of an Authorization header and into the env block of
.mcp.json, and a test named "keeps the token out of an Authorization header written to
disk" locked that in. Both were true. Neither mattered: .mcp.json is shared project
config - Tower's own repo tracks it - so anyone following the documented setup command
and committing their config published a live team token.
Fixed
-
setup --tokennow adds.mcp.jsonto.gitignoreand says plainly that the file
holds a secret, including thegit rm --cached .mcp.jsonneeded when git already tracks
it. Without a token the file stays out of.gitignore, because then it is ordinary
shared config a team is right to commit. -
The local-mode warning no longer recommends the bug 0.10.0 fixed. When
TOWER_URL
was set,serverefused to start and told you to point your agent at a
"type": "http"entry - the exact shape that leaves no process on your machine to
computerepoId, which is how a fork and its upstream split in silence. It now shows
theserve --remoteproxy form. -
tower doctorgreen-lit machines Tower cannot run on. 0.9.1 fixed the Node floor in
requireModernNode, butdoctorcarried its own copy of the naive>= 22.5check - so
the command whose entire job is "is this machine ready?" passed 22.5-22.12 and 23.0-23.3,
the two windows wherenode:sqliteis still behind a flag, and the real command then
died onERR_UNKNOWN_BUILTIN_MODULE. It now callsrequireModernNodedirectly. Its
tests had encoded the wrong floor too, including a "healthy machine" fixture pinned to
v22.5.0. -
init --hooksinstalled five hooks that could never fire. The hook scripts live in
hooks/in a clone; the npm package shipsdist/only. Run from npm, the command wrote
five entries pointing at files that were not there, printed
✔ .claude/settings.json — installed …, and told the user to runnpm run buildin a
project where that script does not exist. Nothing errored, so thePreToolUsehook that
is supposed to block a conflicting edit simply never ran — and the user had every reason
to think they were covered. It now refuses when the scripts are absent and gives the
clone-first steps. The git guards, which shell out tonpx -y tower-mcp, are unaffected
and still work straight from the package. -
The PR collision action had never read a single input. GitHub exposes an input as
INPUT_<NAME>, uppercased with spaces mapped to underscores — hyphens are kept. The
action mapped hyphens too, so it readINPUT_GITHUB_TOKENwhile the runner had set
INPUT_GITHUB-TOKEN;github-token,tower-urlandtower-tokenwere all undefined.
It failed on the token before reaching any collision logic, caught its own throw, printed
::warning::and exited 0 — a green check on an action that did nothing. Surfaced by
opening the repository's first-ever pull request. -
tower --helpexited 1.--help,-handhelpall fell through to the unknown-
command branch: the right text printed, then a failure code.tower --help && …broke,
and so did every smoke test. They are real commands now and exit 0. Baretowerwas
already correct. Caught on the first run of the new packaged-tarball CI job.