Installing through mise does not install v2 #55405

Activity

1. opencode-agent commented on Oct 14, 2026

   

   opencode-agentBot

   on Oct 14, 2026 – with OpenCode Agent

   Contributor

   More actions

   Thanks for the report. I could reproduce this: the GitHub releases mise sees only go up to v1.19.0, because the v2 releases (currently @opencode/cli 2.0.29 on npm) have no GitHub Release with binaries. So:

   • mise use -g github:anomalyco/opencode (from the docs and the landing page) installs 1.19.0.
   • mise use -g opencode (from the README) also installs 1.19.0.

   The latest dev (81d5708) still recommends both commands. The script below reproduces it.

   I also tried mise use -g npm:@opencode/cli. It installs 2.0.28, but then fails with "postinstall script was not run", so it doesn't work as a workaround yet. Until this is sorted out, npm i -g @opencode/cli gets you v2.

   Related:

   • feat(release): publish OpenCode 2 GitHub Releases without taking Latest #54903: open PR to publish v2 GitHub Releases. As written it attaches no binaries and doesn't mark them Latest, so on its own it wouldn't fix mise.
   • [BUG] /update offers 2.0.7 on pacman-managed install, but upgrade cannot work (method undetected; GitHub release v2.0.7 missing) #49660: also found that v2 tags have no GitHub Release.
   • installer: /install silently downgrades existing v2 CLI to v1 #54084: the /install script downgrades v2 to v1, another install path that lands on v1.

   Reproduction script (repro.sh)

   #!/usr/bin/env bash
   # Reproduces anomalyco/opencode#55405: the documented mise install gets v1, not v2.
   set -euo pipefail
   command -v mise >/dev/null || { curl -fsSL https://mise.run | sh; export PATH="$HOME/.local/bin:$PATH"; }
   export MISE_YES=1
   echo "== Latest GitHub release:"; curl -s https://api.github.com/repos/anomalyco/opencode/releases/latest | grep '"tag_name"'
   echo "== Latest @opencode/cli on npm:"; npm view @opencode/cli version
   echo "== Versions mise sees for github:anomalyco/opencode (last 3):"; mise ls-remote github:anomalyco/opencode | tail -3
   mise use -g github:anomalyco/opencode
   echo "== Installed:"; mise exec github:anomalyco/opencode -- opencode --version
   echo "== README variant (mise registry 'opencode'):"
   mise use -g opencode
   mise exec opencode -- opencode --version

   Run it: bash repro.sh
2. opencode-agent

   added

   reproduced

   on Oct 14, 2026
3. opencode-agent commented on Oct 14, 2026

   

   opencode-agentBot

   on Oct 14, 2026 – with OpenCode Agent

   Contributor

   More actions

   A note on how mise support works: OpenCode never maintained mise support itself. The opencode entry in mise's registry is community-maintained by the mise project, and the install line in our docs also came from a community contribution (#2938). In v1 it worked because mise pulled the binaries attached to our GitHub Releases. v2 ships on npm as @opencode/cli, so anything reading GitHub Releases stops at 1.19.0.

   This is now fixed on the mise side. The mise maintainer updated the registry in jdx/mise#14295 so opencode installs 2.x from npm (with the postinstall build allowed) and keeps the GitHub-release backend for 1.x. The change shipped in mise v2026.10.9.

   To get v2:

   mise self-update      # or upgrade mise however you installed it; needs v2026.10.9+
   mise use -g opencode

   Use the opencode shorthand, not github:anomalyco/opencode. The github: backend skips the registry and reads GitHub Releases directly, so it will keep installing 1.19.0 for now.
4. neriousy

   closed this as completedin #55415on Oct 14, 2026