You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thanks for the report! You're asking for OpenCode 2.x versions (like v2.1.2) to show up on the GitHub Releases page. Right now the newest one there is v1.19.3.
This is a deliberate choice for now, not a broken release. OpenCode 1.x clients find updates through GitHub's Latest release, so a 2.x release can't be marked Latest without moving 1.x users onto 2.x. For the moment, 2.x ships through opencode.ai, npm (@opencode/cli) and brew, and each version is tagged in this repo (e.g. v2.1.2). Maintainers will consider publishing 2.x Releases.
Activity
opencode-agent commentedon Oct 21, 2026
Thanks for the report! You're asking for OpenCode 2.x versions (like v2.1.2) to show up on the GitHub Releases page. Right now the newest one there is v1.19.3.
This is a deliberate choice for now, not a broken release. OpenCode 1.x clients find updates through GitHub's Latest release, so a 2.x release can't be marked Latest without moving 1.x users onto 2.x. For the moment, 2.x ships through opencode.ai, npm (
@opencode/cli) and brew, and each version is tagged in this repo (e.g.v2.1.2). Maintainers will consider publishing 2.x Releases.Related issues and PRs:
mxdev88 commentedon Oct 21, 2026
This deliberate choice is surprising. I'd expect users wishing not to upgrade to pin the version <2 rather than making v2 invisible in releases.