Web frontend bundled with opencode-ai@1.18.15 is 1.18.14 (version mismatch: app-version.v1 = 1.18.14)

[changer-changer]

Description

The opencode-ai@1.18.15 npm package ships a binary whose embedded web frontend is 1.18.14, not 1.18.15. The server binary reports "1.18.15" but serves the older frontend chunk (index-DkiM3pJJ.js, which writes app-version.v1 = "1.18.14").

Steps to reproduce

1. Install opencode-ai@1.18.15 (npm).
2. Run opencode web --port 4096 --hostname 0.0.0.0.
3. Open the web UI and check localStorage["app-version.v1"] → shows {"version":"1.18.14"}.
4. Inspect the served HTML → references index-DkiM3pJJ.js (old chunk).

Evidence

• Binary strings (opencode-linux-x64/bin/opencode) contain two frontend bundles:
  • index-DkiM3pJJ.js + index-DkiM3pJJ-fyjg9exh.js → app-version = "1.18.14"
  • index-LbjPUYWZ.js + index-LbjPUYWZ-f2dwhw18.js → "1.18.15"
• The served HTML references only the old chunk: index-DkiM3pJJ.js.
• curl http://127.0.0.1:4096/ returns HTML whose <script src="/_next/static/chunks/index-DkiM3pJJ.js"> corresponds to the 1.18.14 bundle.
• API surface of both bundles is identical (verified by string-diff of all "/..." paths), so API calls work, but the UI runs the older code path.

Impact

• Users on 1.18.15 effectively run the 1.18.14 web UI: any frontend fix shipped between 1.18.14 and 1.18.15 (e.g. session-list / bookmark seeding fixes) is missing.
• Confusing when debugging UI bugs against the reported server version.

Environment

• OS: Ubuntu 22.04 x86_64
• opencode: 1.18.15 (npm opencode-ai)
• Start command: opencode web --port 4096 --hostname 0.0.0.0

[github-actions]

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

• Web UI version number lags: v1.17.17 is displayed when running v1.17.18, it is suspected that the embedded front-end build version is not synchronized #36232: Same symptom — the embedded web frontend bundle version lags the binary version by one release (N-1 pattern), with the same root cause analysis pointing to the frontend build not being synchronized with OPENCODE_VERSION during the release pipeline.

[Skylvw]

Root cause found — this is a release-pipeline ordering bug, and every release is affected, not just 1.18.15.

build-cli checks out the workflow_dispatch commit. The version bump of all package.json files only happens later, in the publish job (script/publish.ts -> prepareReleaseFiles()). So:

• CLI version comes from the OPENCODE_VERSION env (version job output) -> always correct
• Web UI bakes pkg.version from the checked-out packages/app/package.json -> always the previous version on release builds

Evidence for v1.18.15: the released linux-x64 binary contains exactly the chunks (index-DkiM3pJJ.js 2,738.03kB + index-LbjPUYWZ.js 60.15kB) produced by run 31153894817, which built at commit 3255297 where packages/app/package.json was still 1.18.14. The post-bump build (run 31155339513, app 1.18.15) produced different chunks (index-lDgyeTkx.js 2,738.33kB) that never made it into the release — the bump commit only differs from the dispatch commit by the version strings themselves (~300 bytes), so the code is the release code; only the version string is stale.

Also, the "two bundles" observation is normal: every fresh vite build emits two index chunks (a 2.7MB main chunk referenced by index.html plus a ~60kB unreferenced secondary entry chunk).

Fix in #41419: bake the web UI version from OPENCODE_VERSION (same source as the CLI), with a fallback to packages/app/package.json for local dev.