fix(cli): write version-aware plugin entry during installation

[aw338WoWmUI]

Summary

• Installer now writes version-aware plugin entries based on npm dist-tags
• Fixes beta users unexpectedly loading stable version after installation

Problem

When users installed with bunx oh-my-opencode@3.0.0-beta.3 install, the installer wrote "oh-my-opencode" without version. On next OpenCode startup, npm resolved this to latest tag (2.14.0), not the beta version the user intended.

Solution

Query npm dist-tags and write appropriate version suffix:

Installation Command	Writes	Behavior
bunx oh-my-opencode install	@latest	Tracks stable releases
bunx oh-my-opencode@beta install	@beta	Tracks beta tag
bunx oh-my-opencode@3.0.0-beta.2 install	@3.0.0-beta.2	Pins to specific version

Changes

• Added fetchNpmDistTags() to query npm registry for all dist-tags
• Added getPluginNameWithVersion() to determine correct plugin entry format
• Updated addPluginToOpenCodeConfig() to use version-aware entries
• Added comprehensive tests for all scenarios (tag matching, network failure, etc.)

Testing

bun test src/cli/config-manager.test.ts  # 10 tests pass
bun run typecheck                         # No errors

---

Summary by cubic

Fixes the CLI installer to write a version-aware oh-my-opencode plugin entry based on npm dist-tags. This keeps beta/next installs on their intended channel instead of falling back to stable.

• Bug Fixes
  • Query npm dist-tags and write the correct entry:
    • bunx oh-my-opencode install → oh-my-opencode@latest
    • bunx oh-my-opencode@beta install → oh-my-opencode@beta
    • bunx oh-my-opencode@next install → oh-my-opencode@next
    • bunx oh-my-opencode@3.0.0-beta.2 install → oh-my-opencode@3.0.0-beta.2
  • Replace existing plugin entries with the new version-aware value to allow switching channels.
  • Prioritize tags when multiple match the same version: latest > beta > next.
  • Fallback to a pinned version on registry/network errors with a 5s timeout.

^{Written for commit 8395a6e. Summary will update on new commits.}

[github-actions]

All contributors have signed the CLA. Thank you! ✅
_{Posted by the CLA Assistant Lite bot.}

[greptile-apps]

Your free trial has ended. If you'd like to continue receiving code reviews, you can add a payment method here.

[cubic-dev-ai]

1 issue found across 3 files

Confidence score: 3/5

• Installer currently aborts if any oh-my-opencode plugin entries exist in src/cli/config-manager.ts, so users can’t switch channels or versions and stale plugin definitions persist—this is a real regression risk for updates.
• Pay close attention to src/cli/config-manager.ts - ensure the installer updates existing plugin entries instead of exiting early.

Prompt for AI agents (all issues)

Check if these issues are valid — if so, understand the root cause of each and fix them.


<file name="src/cli/config-manager.ts">

<violation number="1" location="src/cli/config-manager.ts:240">
P1: Installer exits when any oh-my-opencode plugin exists, so it never updates the entry to the requested version/tag, blocking channel/version switches and leaving stale plugin entries.</violation>
</file>

---

Since this is your first cubic review, here's how it works:

• cubic automatically reviews your code and comments on bugs and improvements
• Teach cubic by replying to its comments. cubic learns from your replies and gets better over time
• Ask questions if you need clarification on any suggestion

_{Reply with feedback, questions, or to request a fix. Tag @cubic-dev-ai to re-run a review.}

[aw338WoWmUI]

recheck

[kdcokenny]

Thanks! This solves a real pain point for our beta users. The implementation is clean and the test coverage is excellent. 👍
A few minor thoughts:

1. Tag ordering: Object.entries(distTags) iteration order isn't guaranteed. If a version matches multiple tags (e.g., during release promotion when latest and beta temporarily point to the same version), the result could be non-deterministic. Please prioritize the latest explicitly:

      const prioritizedTags = ['latest', 'beta', 'next', ...Object.keys(distTags)]
   for (const tag of prioritizedTags) {
     if (distTags[tag] === currentVersion) {
       return `${PACKAGE_NAME}@${tag}`
     }
   }

2. Fetch timeout: Might be worth adding signal: AbortSignal.timeout(5000) to avoid blocking installation on slow networks.
3. Also, I believe that there are some unused imports that should be cleaned up.
4. Please resolve the merge conflicts

[aw338WoWmUI]

recheck

[kdcokenny]

lgtm, thanks for the contribution! 🚀