[v2] cli: update prompt recommends older version #47714

Activity

1. github-actions

   assigned

   jlongster

   on Sep 7, 2026
2. github-actions commented on Sep 7, 2026

   

   github-actionsBot

   on Sep 7, 2026 – with GitHub Actions

   Contributor

   More actions

   This issue might be a duplicate of existing issues. Please check:

   • Desktop v1.17.2 prompts to 'update' to older v1.17.1 (downgrade offered as upgrade) #31735: Desktop v1.17.2 prompts to 'update' to older v1.17.1 (downgrade offered as upgrade) — same root cause: the update check recommends an older version instead of correctly detecting the installed version is already newer.
3. opencode-agent

   added

   2.0

   on Sep 7, 2026
4. ZaraByte commented on Sep 19, 2026

   

   ZaraByte

   on Sep 19, 2026

   More actions

   Another instance of this, with a different shape: a 2.0.9 install was downgraded to 2.0.8 because the update service's answer for current=2.0.9 moved backwards.

   Environment

   • opencode version: 2.0.9 → 2.0.8 (installed automatically at 2026-09-19 09:21:29 UTC)
   • OS: Windows 11 (Windows_NT 10.0.26200, win32 x64)
   • Install/channel: bun global install (~/.bun/bin), channel latest, local=false
   • Active plugins: none at the time (a plugin was installed later that day)

   Evidence

   CLI log (~/.local/share/opencode/log/opencode.log, UTC):

   09:21:10 level=INFO message="update check" current=2.0.9 latest=2.0.8
   09:21:10 level=INFO message="OpenCode update available" current=2.0.9 latest=2.0.8 action=notify
   09:21:24 level=INFO message="spawning process" command=bun args="[... \"install\",\"--global\",\"--trust\",\"--cache-dir\",\"C:\\Users\\<user>\\.cache\\opencode\\update-268SSX\",\"@opencode/cli@2.0.8\"]"
   09:21:29 level=INFO message="updated OpenCode" from=2.0.9 to=2.0.8 method=bun
   

   Earlier the same day the same check reported current=2.0.9 latest=2.0.9 (action=up-to-date, 08:54:53 UTC), so the service's "latest" for latest/cli/npm changed from 2.0.9 to 2.0.8 between 08:54 and 09:21 UTC.

   The update API still answers this way (checked 2026-09-19 ~09:35 UTC):

   $ curl -s "https://opencode.ai/update/api/latest/cli/npm?current=2.0.9"
   {"channel":"latest","name":"cli","distribution":"npm","version":"2.0.8","metadata":{"package":"@opencode/cli","github":{"sha":"0a611129...","run_id":"35325251492","run_attempt":"1","actor":"Hona","ref":"refs/heads/v2"}},"active":false,"minimum":false,"time_created":1789722595958,"time_updated":1789722595958}
   

   Meanwhile @opencode/cli@2.0.9 is published on npm (dist-tag latest, published 2026-09-19T05:11:15Z) and v2.0.9 is tagged in the repo. So any client on 2.0.9 is currently told that 2.0.8 is "available".

   Expected

   The update prompt/install should only fire when latest > current (semver-greater), so a client that is ahead of the update service can never be downgraded.

   Actual

   2.0.9 was downgraded to 2.0.8; OpenCode even logged it as updated OpenCode from=2.0.9 to=2.0.8. (Same missing semver-gt guard noted in #49660.)