chore(deps): bump cloned OpenCode source to v1.15.1#382
Merged
Conversation
Updates the locally-inspected OpenCode upstream from v1.14.41 (2026-05-12) to v1.15.1 (2026-05-16). Pure tooling artifact for internal inspection only; no shipped behavior changes. The manifest reason for the @opencode-ai/plugin entry is also refined to point at the multi-source plugin-loader topology question that this clone helped resolve empirically.
fro-bot
approved these changes
May 16, 2026
Collaborator
fro-bot
left a comment
fro-bot
left a comment
There was a problem hiding this comment.
Verdict: PASS
This is a pure metadata bump of a read-only, gitignored inspection clone. No runtime code, no plugin API surface, no TypeScript, no shipped assets changed.
Blocking issues
None
Non-blocking concerns
None
Missing tests
None — no testable logic changed.
Risk assessment: LOW
- All changed lines are in (version/ref strings + reason prose) and (one line updating the version reference).
- The cloned repos directory is gitignored and does not ship in the npm package.
- No plugin hooks, config schema, skill/agent assets, or build scripts were touched.
- The PR description confirms
bun scripts/content-integrity.tspasses, tag was verified viagit ls-remote, and the origin URL matches the approved remote. - Zero blast radius for downstream consumers.
Run Summary
| Field | Value |
|---|---|
| Event | pull_request |
| Repository | marcusrbrown/systematic |
| Run ID | 25958162398 |
| Cache | hit |
| Session | ses_1cff0cde4ffeccsdDq0ud5s8d1 |
fro-bot
approved these changes
May 16, 2026
Collaborator
fro-bot
left a comment
fro-bot
left a comment
There was a problem hiding this comment.
Verdict: PASS
This is a pure metadata bump of a read-only, gitignored inspection clone. No runtime code, no plugin API surface, no TypeScript, no shipped assets changed.
Blocking issues
None
Non-blocking concerns
None
Missing tests
None — no testable logic changed.
Risk assessment: LOW
- All changed lines are in
.slim/clonedeps.json(version/ref strings + reason prose) andAGENTS.md(one line updating the version reference). - The cloned repos directory is gitignored and does not ship in the npm package.
- No plugin hooks, config schema, skill/agent assets, or build scripts were touched.
- The PR description confirms
bun scripts/content-integrity.tspasses, tag was verified viagit ls-remote, and the origin URL matches the approved remote. - Zero blast radius for downstream consumers.
Run Summary
| Field | Value |
|---|---|
| Event | pull_request |
| Repository | marcusrbrown/systematic |
| Run ID | 25958162398 |
| Cache | hit |
| Session | ses_1cff0cde4ffeccsdDq0ud5s8d1 |
Collaborator
|
Already reviewed and approved in this session (Run ID 25958162398). No additional action taken. Run Summary
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bumps the locally-inspected OpenCode upstream source from
v1.14.41(2026-05-12) tov1.15.1(2026-05-16) under.slim/clonedeps/repos/anomalyco__opencode/.This is a tooling artifact — read-only source kept around so I can inspect plugin-loader internals, the SDK runtime client, and other upstream surfaces directly. The pinned clone does not ship as part of the npm package and does not affect runtime behavior.
Why bump now
I needed to verify the plugin-loader topology (specifically
PluginInput.clientlifetime and how multi-source plugin loads share state) against the freshest upstream. The empirical finding —clientis built once per OpenCode process atpackages/opencode/src/plugin/index.ts:128-150and shared by reference across every plugin factory — sharpened the design of an upcoming memoization plan.What changed
.slim/clonedeps/repos/anomalyco__opencode/checked out tov1.15.1(SHAbe12b43) via shallow fetch; previouslyv1.14.41(SHA8ba2a91). 10 upstream releases bridged (v1.14.42–v1.14.51, v1.15.0, v1.15.1)..slim/clonedeps.jsonupdated:@opencode-ai/sdk,@opencode-ai/plugin) bumped toresolvedVersion: "1.15.1"andref: "v1.15.1"AGENTS.mdupdated to referencev1.15.1in the Cloned Dependency Source sectionVerification
v1.15.1verified upstream viagit ls-remotebefore fetchhttps://github.com/anomalyco/opencode.git)--depth=1 --no-tags); clone footprint grew from 137M to 152Mpackages/sdk/jsandpackages/pluginstill present at the new tagbun scripts/content-integrity.tspasses — no banned-pattern regressions from the upstream content.gitignoreand.ignoremarker blocks unchanged — git still ignoresrepos/, OpenCode can still read itRelease impact
None. The
chore(deps):prefix triggers no semantic-release bump per the project's release rules;.slim/clonedeps/repos/is gitignored and the only tracked changes are the two metadata files above.