Plugins using npm dist-tags (e.g. @dev) never auto-update due to bun lockfile caching #12712

Activity

1. github-actions

   assigned

   thdxr

   on Feb 8, 2026
2. github-actions commented on Feb 8, 2026

   

   github-actionsbot

   on Feb 8, 2026 – with GitHub Actions

   Contributor

   More actions

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

   • Plugins with npm dist-tags other than @latest never update on restart #12312: Plugins with npm dist-tags other than @latest never update on restart

   Feel free to ignore if none of these address your specific case.
3. ErcinDedeoglu commented on Feb 8, 2026

   

   ErcinDedeoglu

   on Feb 8, 2026

   Author

   More actions

   Root Cause Found

   The issue is in BunProc.install() at packages/opencode/src/bun/index.ts line 78:

   if (dependencies[pkg] === version && modExists) return mod

   This compares the cached specifier in ~/.cache/opencode/package.json against the config specifier. The install command uses bun add --force --exact:

   const args = ["add", "--force", "--exact", "--cwd", Global.Path.cache, pkg + "@" + version]

   The problem is how bun add --exact writes different dist-tags to package.json:

   Config specifier	bun add --exact writes to package.json	=== "latest"	=== "dev"	Behavior
   my-plugin@latest	"3.3.2" (resolved semver)	"3.3.2" === "latest" → false	—	Always re-installs ✅
   my-plugin@dev	"dev" (literal tag)	—	"dev" === "dev" → true	Skips forever ❌
   my-plugin@beta	"beta" (literal tag)	—	—	Skips forever ❌
   my-plugin@canary	"canary" (literal tag)	—	—	Skips forever ❌

   bun add --exact only resolves @latest to a concrete version. All other dist-tags (@dev, @beta, @next, @canary, etc.) are written literally, which means the === check always passes and the plugin never updates.

   @latest accidentally self-heals because the cached value (e.g. "3.3.2") never string-matches "latest", forcing a re-install on every startup.

   Suggested Fix

   For non-latest dist-tags, the equality check needs to resolve the tag before comparing, or alternatively always re-run bun add when the specifier is a dist-tag (not a semver):

   function isDistTag(version: string): boolean {
     // dist-tags are non-semver strings like "dev", "beta", "next", "canary"
     return !/^[\d^~>=<]/.test(version) && version !== "latest"
   }
   
   // In install():
   if (dependencies[pkg] === version && modExists && !isDistTag(version)) return mod

   This would make all dist-tags behave like @latest — always re-resolve on startup.
4. github-actions commented on Apr 10, 2026

   

   github-actionsbot

   on Apr 10, 2026 – with GitHub Actions

   Contributor

   More actions

   To stay organized issues are automatically closed after 90 days of no activity. If the issue is still relevant please open a new one.
5. github-actions

   closed this as completedon Apr 10, 2026