Skip to content

0.10.1 - six things that were silently broken for every user

Choose a tag to compare

@Rohanxmalik Rohanxmalik released this 30 Sep 00:30
· 16 commits to main since this release

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 --token now adds .mcp.json to .gitignore and says plainly that the file
    holds a secret, including the git rm --cached .mcp.json needed 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, serve refused 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
    compute repoId, which is how a fork and its upstream split in silence. It now shows
    the serve --remote proxy form.

  • tower doctor green-lit machines Tower cannot run on. 0.9.1 fixed the Node floor in
    requireModernNode, but doctor carried its own copy of the naive >= 22.5 check - so
    the command whose entire job is "is this machine ready?" passed 22.5-22.12 and 23.0-23.3,
    the two windows where node:sqlite is still behind a flag, and the real command then
    died on ERR_UNKNOWN_BUILTIN_MODULE. It now calls requireModernNode directly. Its
    tests had encoded the wrong floor too, including a "healthy machine" fixture pinned to
    v22.5.0.

  • init --hooks installed five hooks that could never fire. The hook scripts live in
    hooks/ in a clone; the npm package ships dist/ 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 run npm run build in a
    project where that script does not exist. Nothing errored, so the PreToolUse hook 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 to npx -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 read INPUT_GITHUB_TOKEN while the runner had set
    INPUT_GITHUB-TOKEN; github-token, tower-url and tower-token were 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 --help exited 1. --help, -h and help all 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. Bare tower was
    already correct. Caught on the first run of the new packaged-tarball CI job.