Description
The published changelog only covers v1. The newest entry is v1.18.33 (Sep 28, 2026), and there are no entries for any v2.0.x release, so v2 users have no published release notes.
v2.0.20 has a GitHub release whose body is only release: v2.0.20 — no notes. And https://opencode.ai/v2/changelog returns 404.
I wanted to see what changed in v2.0.20 and had to diff the tags myself (v2.0.19...v2.0.20 via the compare API: 31 commits, 179 files).
Environment
- opencode version: 2.0.20 (channel: latest)
- OS: Debian 13 (trixie), Linux 6.12.107 x86_64
- Terminal: xterm-256color, COLORTERM=truecolor
- Shell: /bin/bash
- Active plugins: opencode-memento, opencode2-skill-creator, opencode-awake, @tarquinen/opencode-dcp@3.2.0
Steps to reproduce
opencode --version reports opencode v2.0.20
- Open https://opencode.ai/changelog
- The most recent entry is v1.18.33 (Sep 28, 2026). No v2.0.x entries appear anywhere on the page
- Open https://github.com/anomalyco/opencode/releases/tag/v2.0.20 — the release body is only
release: v2.0.20
- Open https://opencode.ai/v2/changelog — returns 404
Expected Behavior
v2 releases appear in the changelog with the same Core / TUI / Desktop breakdown the v1 entries use, or the GitHub release body carries the notes.
Actual Behavior
No published notes exist for any v2.0.x release. The only way to find out what changed is to diff tags (git log v2.0.19..v2.0.20, or the GitHub compare API).
Additional Context
Both lines appear to be in active maintenance — the v1.18.24 notes mention "V1 now reads supported V2 config fields" — so the single changelog silently omits all v2 work.
For scale, v2.0.20 alone is 31 commits across 179 files, including user-visible changes: a separate ChatGPT token-sharing OAuth method, new opencode auth export / auth import commands, changed permission-rejection behavior in opencode run, provider response bodies preserved in session errors, and database files restricted to their owner.
Not urgent — I worked around it with the compare API. Reporting because the changelog reads as though development stopped at v1, and gives no hint that a v2 track exists.
Description
The published changelog only covers v1. The newest entry is v1.18.33 (Sep 28, 2026), and there are no entries for any v2.0.x release, so v2 users have no published release notes.
v2.0.20 has a GitHub release whose body is only
release: v2.0.20— no notes. And https://opencode.ai/v2/changelog returns 404.I wanted to see what changed in v2.0.20 and had to diff the tags myself (
v2.0.19...v2.0.20via the compare API: 31 commits, 179 files).Environment
Steps to reproduce
opencode --versionreportsopencode v2.0.20release: v2.0.20Expected Behavior
v2 releases appear in the changelog with the same Core / TUI / Desktop breakdown the v1 entries use, or the GitHub release body carries the notes.
Actual Behavior
No published notes exist for any v2.0.x release. The only way to find out what changed is to diff tags (
git log v2.0.19..v2.0.20, or the GitHub compare API).Additional Context
Both lines appear to be in active maintenance — the v1.18.24 notes mention "V1 now reads supported V2 config fields" — so the single changelog silently omits all v2 work.
For scale, v2.0.20 alone is 31 commits across 179 files, including user-visible changes: a separate ChatGPT token-sharing OAuth method, new
opencode auth export/auth importcommands, changed permission-rejection behavior inopencode run, provider response bodies preserved in session errors, and database files restricted to their owner.Not urgent — I worked around it with the compare API. Reporting because the changelog reads as though development stopped at v1, and gives no hint that a v2 track exists.