Skip to content

Tags: utmstack/utmstack-cli

Tags

v1.0.3

Toggle v1.0.3's commit message
Fix the wordmark: UTMStack, not UTMSSTACK

The split TUI logo duplicated the S — left half was "UTMS" and right half
"STACK", rendering "UTMSSTACK". Replaced all three logo sites with the correct
figlet: "UTM" in shaded blocks (left, muted) + "STACK" in solid blocks (right,
bright), which reads "UTMSTACK".

  - packages/tui/src/logo.ts        — startup/home logo (the one in the screenshot)
  - packages/opencode/src/cli/ui.ts — the --help wordmark
  - packages/tui/src/util/presentation.ts — session-epilogue logo (was still
    opencode's), plus the "opencode -s" continue hint -> "utmstack -s"

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

v1.0.2

Toggle v1.0.2's commit message
README: document the real Windows story (x64 native, ARM64 via emulat…

…ion)

Reverts the WSL-required framing. Windows uses the x64 build — native on x64,
under emulation on ARM64, where the TUI works. No native ARM64 build ships
because it cannot start the renderer (same limitation as opencode's own).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

v1.0.1

Toggle v1.0.1's commit message
Type the BUILD_TARGETS filter params (fix typecheck / pre-push hook)

targetKey's parameter was implicitly any, which failed `bun typecheck` and
blocked the pre-push hook, so the 1.3.13 Windows fix never reached the remote.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

v1.0.0

Toggle v1.0.0's commit message
Retry flaky baseline builds, and never lose a platform to one

The windows-x64 job died on "Failed to extract executable for
bun-windows-x64-baseline-v1.3.14. The download may be incomplete." Building the
no-AVX2 variant makes Bun fetch extra cross-compilation artifacts, and that
fetch is known-flaky — opencode's own build script calls it out.

The build now retries three times, and if the baseline variant still will not
download, falls back to building the native binary alone rather than failing
the platform outright. The installer only requests -baseline on non-AVX2 x64
hardware; everyone else is served by the native asset, so a missing baseline
should degrade coverage, not erase the platform.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>