[FEATURE]: lockfiles (or similar) support for plugins #6511

Open
opened 2026-02-16 18:04:26 -05:00 by yindo · 1 comment
Owner

Originally created by @MaxLeiter on GitHub (Jan 16, 2026).

Originally assigned to: @thdxr on GitHub.

Feature hasn't been suggested before.

  • I have verified this feature I'm about to request hasn't been suggested before.

Describe the enhancement you want to request

(if this has been suggested before, sorry. I did search)

I noticed that some plugins recommend installing them with @latest. I'm aware of the previous npm supply chain issues so I won't be doing that, but I assume a fair amount of people are. It'd be great to have some sort of lockfile support or "Are you sure you want to upgrade?" prompt if someone does use @latest or similar un-pinned versions. Of course, people might just blindly accept those prompts, but I think its worth a little effort here given the potential risks.

Originally created by @MaxLeiter on GitHub (Jan 16, 2026). Originally assigned to: @thdxr on GitHub. ### Feature hasn't been suggested before. - [x] I have verified this feature I'm about to request hasn't been suggested before. ### Describe the enhancement you want to request (if this has been suggested before, sorry. I did search) I noticed that some plugins [recommend installing them with `@latest`](https://github.com/mohak34/opencode-notifier). I'm aware of the previous npm supply chain issues so I won't be doing that, but I assume a fair amount of people are. It'd be great to have some sort of lockfile support or "Are you sure you want to upgrade?" prompt if someone _does_ use `@latest` or similar un-pinned versions. Of course, people might just blindly accept those prompts, but I think its worth a little effort here given the potential risks.
yindo added the discussion label 2026-02-16 18:04:26 -05:00
Author
Owner

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

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

  • #8763: Plugin loader incorrectly appends @latest to GitHub references (related issue about @latest handling)
  • #6774: Plugins with implied latest version don't auto-update on restart (related to version pinning and defaults to @latest)
  • #6159: Plugin Auto-Update Feature (broader feature request for automatic plugin update management with version control)

These issues address related concerns about plugin versioning, pinning, and handling of unpinned/@latest versions. Your proposal for lockfile support could complement or address concerns raised in these existing issues.

Feel free to ignore if your specific case requires a different approach.

@github-actions[bot] commented on GitHub (Jan 16, 2026): This issue might be a duplicate of existing issues. Please check: - #8763: Plugin loader incorrectly appends @latest to GitHub references (related issue about @latest handling) - #6774: Plugins with implied latest version don't auto-update on restart (related to version pinning and defaults to @latest) - #6159: Plugin Auto-Update Feature (broader feature request for automatic plugin update management with version control) These issues address related concerns about plugin versioning, pinning, and handling of unpinned/@latest versions. Your proposal for lockfile support could complement or address concerns raised in these existing issues. Feel free to ignore if your specific case requires a different approach.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: anomalyco/opencode#6511