fix(auto-update): use USER_CONFIG_DIR instead of CACHE_DIR for plugin invalidation #1424
+55
−56
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.
Summary
Fixes auto-update failing silently due to operating on wrong directory.
Problem
The auto-update-checker was using
CACHE_DIR(/.cache/opencode) for plugin invalidation, but plugins are actually installed in/.config/opencode).USER_CONFIG_DIR(Symptom: "Update available" toast appears, but after restart the old version is still installed.
Root cause:
invalidatePackage()tried to remove package from~/.cache/opencode/node_modules/(wrong!)removeFromBunLock()tried to modify~/.cache/opencode/bun.lock(wrong!)bun installran in correct dir but respected existing lockfile → old version reinstalledFix
invalidatePackage()to useUSER_CONFIG_DIRremoveFromBunLock()to useUSER_CONFIG_DIRINSTALLED_PACKAGE_JSONconstant to useUSER_CONFIG_DIRTesting
bun test src/hooks/auto-update-checker/)Summary by cubic
Fixes auto-update by using USER_CONFIG_DIR for plugin invalidation and lockfile edits so updates apply after restart instead of failing silently.
Written for commit 9c2c109. Summary will update on new commits.