v0.4.1

Tower v0.4.1

Package: @tower-org/cli@0.4.1
Source commit: a698d587abbb176f564eb765bcf986f2f86102dc

What's changed

Changed

• Pushing a stable v<version> tag now starts the production release workflow
  automatically. GitHub environment approval remains required before npm and
  GitHub Release publication.
• The protected publication job validates and publishes the npm tarball built
  before approval instead of rebuilding the application and rerunning release
  gates.
• Production Releases publish install.sh, install.ps1, and SHA256SUMS as
  top-level helper assets. The changelog remains the release-notes source, and
  the CMD compatibility wrapper remains inside the Windows portable archive.
  Installers now report clear download, verification, extraction, and activation
  progress.

Fixed

• GitHub Pages retries use attempt-scoped artifacts, preventing a failed
  deployment retry from colliding with an artifact uploaded by the prior attempt.
• Fresh Workbench sessions no longer re-inject resolved historical batches and
  trigger duplicate reviews.
• Completing a task from Missions now preserves its running execution, terminal,
  and worktree when a merge conflict occurs, sends resolution instructions to
  the current agent, and allows completion to be retried after the conflict is
  resolved.
• Codex connection checks now use isolated, ephemeral probes with user settings
  and execution tools disabled, preventing checks from affecting normal sessions.
• First-run setup keeps optional extensions unselected by default, opens the first
  workspace directly after completion, and restores the finish action after a
  save error so setup can be retried.
• Guided Tour highlights and actions now follow the active primary theme instead
  of using a fixed amber accent.
• Development type checks now include Next.js declarations generated under the
  custom .next-dev output directory.

The npm package with provenance remains the standard registry channel. The tower-org-cli-0.4.1.tgz asset is the exact npm pack input for audit and offline npm clients; it still requires npm dependency resolution. Use a platform portable asset for a registry-free installation. GitHub's automatic source archives are source code, not Tower installers.

Portable targets

OS	CPU	Asset
darwin	arm64	tower-portable-darwin-arm64.tar.gz
darwin	x64	tower-portable-darwin-x64.tar.gz
linux	arm64	tower-portable-linux-arm64.tar.gz
linux	x64	tower-portable-linux-x64.tar.gz
windows	x64	tower-portable-windows-x64.tar.gz

Every listed target passed a native runner smoke covering first database creation, migrations, Prisma Client/Query/Schema Engines, MCP startup, node-pty, ripgrep, and Tower HTTP startup with npm/Prisma download endpoints blocked. Targets that do not pass are not assembled or published.

Node.js

Node.js >=22.0.0 is required and is not bundled or installed by Tower. Node 22 and 24 are tested on every release target. Other versions meeting the minimum continue in best-effort mode unless listed as specifically incompatible.

Verify

Download the asset and SHA256SUMS, then filter the selected filename and run sha256sum -c - (Linux) or shasum -a 256 -c - (macOS); on Windows compare Get-FileHash <asset> -Algorithm SHA256 with the matching line in SHA256SUMS. Review install.sh or install.ps1 before execution.

Install and recovery

The versioned download base is https://github.com/tower-org/tower/releases/download/v0.4.1. On Windows run install.ps1 from PowerShell; use a process-scoped -ExecutionPolicy Bypass only when local policy requires it. Pass --version 0.4.1 / -Version 0.4.1 to pin this release. The installers support --rollback / -Rollback and --uninstall / -Uninstall; uninstall preserves ~/.tower user data. The maintained installation guide is https://tower-org.github.io/tower/guide/getting-started.html (English: https://tower-org.github.io/tower/en/guide/getting-started.html).