Skip to content

Track OpenCode 1.18.12 - #7

Merged
btriapitsyn merged 2 commits into
mainfrom
chore/track-opencode-1-18-12
Aug 6, 2026
Merged

Track OpenCode 1.18.12#7
btriapitsyn merged 2 commits into
mainfrom
chore/track-opencode-1-18-12

Conversation

@btriapitsyn

Copy link
Copy Markdown
Collaborator

Why

OpenChamber moved to SDK 1.18.12; this package still asked for plugin API 1.18.8, whose own SDK dependency is 1.18.8.

Two versions of the same SDK in one dependency tree stopped the Electron package from building: the packager walks production dependencies and could not resolve the nested one.

Production dependency @opencode-ai/sdk not found for package @opencode-ai/plugin

Safety

The workspace surface is unchanged across these releases. Compared 1.18.8 with 1.18.12:

  • dist/v2/client.d.ts — identical workspace API
  • dist/gen/sdk.gen.d.ts — identical
  • dist/v2/gen/types.gen.d.ts — identical workspace types

Nothing in this package had to adapt. The runtime image tracks the same version, so the OpenCode CLI inside a workspace matches the API the host talks to.

Tests

Unchanged: the same three Windows-only suites fail before and after (symlinks, POSIX modes), green in Linux CI.

OpenChamber moved to SDK 1.18.12 while this package still asked for plugin API
1.18.8, whose own SDK dependency is 1.18.8. Two versions of the same SDK in one
dependency tree stopped the Electron package from building at all: the packager
walks production dependencies and could not resolve the nested one.

The workspace surface is unchanged across those releases — the v2 client, the
generated SDK and the generated types carry the same workspace API and types, so
nothing in this package had to adapt. The runtime image tracks the same version,
so the CLI inside a workspace matches the API the host talks to.
`@opencode-ai/plugin` appears exactly once in this package, as an `import type`
in `src/plugin.d.ts`. No runtime code loads it. Declaring it under
`dependencies` made it part of every consumer's production tree, so the Electron
packager walked it and demanded its transitive SDK — which, once OpenChamber
moved to 1.18.12 while this package asked for 1.18.8, could not be resolved and
stopped the package from building at all.

Aligning the versions removes today's mismatch; moving the dependency removes
the reason a mismatch could break packaging in the first place. This package now
ships no production dependencies, which is what a plugin loaded by its host
should look like.
@btriapitsyn
btriapitsyn merged commit 43e2450 into main Aug 6, 2026
7 checks passed
@btriapitsyn
btriapitsyn deleted the chore/track-opencode-1-18-12 branch August 6, 2026 15:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants