anomalyco/opencode
1
0
Fork 0
mirror of https://github.com/anomalyco/opencode.git synced 2026-07-22 02:05:26 -04:00
Code Issues 5.9k Packages Projects Releases 19 Wiki Activity

opencode upgrade doesn't update plugin dependencies in ~/.config/opencode/package.json #7476

New Issue
Open
opened 2026-02-16 18:07:18 -05:00 by yindo · 1 comment
yindo commented 2026-02-16 18:07:18 -05:00
Owner
Copy Link
Copy Source

Originally created by @cbingb666 on GitHub (Jan 24, 2026).

Originally assigned to: @thdxr on GitHub.

Description

opencode upgrade successfully updates OpenCode binary but fails to update plugin dependencies in `~/.config/opencode/package.json`.

Observed behavior:

After running `opencode upgrade`, the command reports success and the binary is upgraded:

  • `opencode --version` shows new version (e.g., 1.1.34) ✓
  • `/opt/homebrew/bin/opencode` symlink points to new version ✓

However, the plugin dependency remains outdated:

  • `~/.config/opencode/package.json` still has `"@opencode-ai/plugin": "1.1.31"` ✗
  • `~/.config/opencode/node_modules/@opencode-ai/plugin/package.json` shows old version ✗

Expected behavior:

`opencode upgrade` should update both:

  1. The OpenCode binary
  2. The plugin dependencies in `~/.config/opencode/package.json`

This causes a version mismatch between the CLI and its plugin, potentially leading to compatibility issues or unexpected behavior.

Plugins

  • oh-my-opencode
  • opencode-antigravity-auth@1.3.1

OpenCode version

1.1.34 (after upgrade)

Steps to reproduce

  1. Install OpenCode via Homebrew with plugin dependencies at version 1.1.31
  2. Run `opencode upgrade`
  3. Observe:
    • Binary upgrades successfully to 1.1.34
    • `opencode --version` shows 1.1.34
  4. Check plugin version:
    ```bash
    cat ~/.config/opencode/package.json # Shows "@opencode-ai/plugin": "1.1.31"
    ```
  5. Manually update plugin:
    ```bash
    cd ~/.config/opencode
    bun add @opencode-ai/plugin@1.1.34
    ```
  6. Now plugin version matches binary version

Workaround:

Users need to manually update the plugin with:
```bash
cd ~/.config/opencode
bun add @opencode-ai/plugin@latest
```

Screenshot and/or share link

```bash

Before upgrade

$ opencode --version
1.1.31

$ opencode upgrade
(ASCII art shown)
┌ Upgrade
│
● Using method: brew
│
● From 1.1.31 → 1.1.34
│
◇ Upgrade complete
│
└ Done

After upgrade - binary updated

$ opencode --version
1.1.34

But plugin not updated

$ cat ~/.config/opencode/package.json
{
"dependencies": {
"@opencode-ai/plugin": "1.1.31" # <- Still old!
}
}

$ ls ~/.config/opencode/node_modules/@opencode-ai/plugin/package.json
...version": "1.1.31" # <- Still old!
```

Operating System

macOS 15.3 (Apple Silicon)

Terminal

iTerm2

Originally created by @cbingb666 on GitHub (Jan 24, 2026). Originally assigned to: @thdxr on GitHub. ### Description `opencode upgrade` successfully updates OpenCode binary but fails to update plugin dependencies in \`~/.config/opencode/package.json\`. **Observed behavior:** After running \`opencode upgrade\`, the command reports success and the binary is upgraded: - \`opencode --version\` shows new version (e.g., 1.1.34) ✓ - \`/opt/homebrew/bin/opencode\` symlink points to new version ✓ However, the plugin dependency remains outdated: - \`~/.config/opencode/package.json\` still has \`"@opencode-ai/plugin": "1.1.31"\` ✗ - \`~/.config/opencode/node_modules/@opencode-ai/plugin/package.json\` shows old version ✗ **Expected behavior:** \`opencode upgrade\` should update both: 1. The OpenCode binary 2. The plugin dependencies in \`~/.config/opencode/package.json\` This causes a version mismatch between the CLI and its plugin, potentially leading to compatibility issues or unexpected behavior. ### Plugins - oh-my-opencode - opencode-antigravity-auth@1.3.1 ### OpenCode version 1.1.34 (after upgrade) ### Steps to reproduce 1. Install OpenCode via Homebrew with plugin dependencies at version 1.1.31 2. Run \`opencode upgrade\` 3. Observe: - Binary upgrades successfully to 1.1.34 - \`opencode --version\` shows 1.1.34 4. Check plugin version: \`\`\`bash cat ~/.config/opencode/package.json # Shows "@opencode-ai/plugin": "1.1.31" \`\`\` 5. Manually update plugin: \`\`\`bash cd ~/.config/opencode bun add @opencode-ai/plugin@1.1.34 \`\`\` 6. Now plugin version matches binary version **Workaround:** Users need to manually update the plugin with: \`\`\`bash cd ~/.config/opencode bun add @opencode-ai/plugin@latest \`\`\` ### Screenshot and/or share link \`\`\`bash # Before upgrade $ opencode --version 1.1.31 $ opencode upgrade (ASCII art shown) ┌ Upgrade │ ● Using method: brew │ ● From 1.1.31 → 1.1.34 │ ◇ Upgrade complete │ └ Done # After upgrade - binary updated $ opencode --version 1.1.34 # But plugin not updated $ cat ~/.config/opencode/package.json { "dependencies": { "@opencode-ai/plugin": "1.1.31" # <- Still old! } } $ ls ~/.config/opencode/node_modules/@opencode-ai/plugin/package.json ...version": "1.1.31" # <- Still old! \`\`\` ### Operating System macOS 15.3 (Apple Silicon) ### Terminal iTerm2
yindo commented 2026-02-16 18:07:18 -05:00
Author
Owner
Copy Link
Copy Source

@github-actions[bot] commented on GitHub (Jan 24, 2026):

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

  • #8422: opencode upgrade reports success every time - The upgrade command appears to have validation/success reporting issues
  • #5375: opencode upgrade doesnt move to newest version - Related upgrade command functionality issues
  • #6774: Plugins with implied latest version don't auto-update on restart - Related to plugin dependency versioning not being properly updated
  • #8729: Disable force dependency update while starting - Related to how plugin dependencies are managed and installed

Feel free to ignore if none of these address your specific case.

@github-actions[bot] commented on GitHub (Jan 24, 2026): This issue might be a duplicate of existing issues. Please check: - #8422: `opencode upgrade` reports success every time - The upgrade command appears to have validation/success reporting issues - #5375: `opencode upgrade` doesnt move to newest version - Related upgrade command functionality issues - #6774: Plugins with implied latest version don't auto-update on restart - Related to plugin dependency versioning not being properly updated - #8729: Disable force dependency update while starting - Related to how plugin dependencies are managed and installed Feel free to ignore if none of these address your specific case.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
acp
bad
bug
discussion
docs
documentation
enhancement
extension
good first issue
growth
help-wanted
mcp
model-problem
needs:compliance
nix
opentui
perf
pull-request
Mirrored from GitHub Pull Request
 tui
web
windows
zen
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: anomalyco/opencode#7476
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?