Summary
Add a per-plugin way to exclude selected plugins from /pp updateAll, while keeping them tracked by Plugin Portal for listing, recognition, and manual updates.
Credit to Zoriot for the report.
Problem
Some server owners need to hold back a specific plugin version even when newer marketplace versions exist. Today /pp updateAll considers every tracked local plugin and has no per-plugin skip/pin mechanism. The only workaround is to stop tracking the plugin in Plugin Portal metadata, which is not ideal because it also loses normal Plugin Portal management context.
A concrete example is a plugin releasing an update that breaks worlds or server behavior, where the owner still wants to update other plugins safely.
Proposed behavior
- Add a per-plugin update exclusion or pin flag for locally tracked plugins.
/pp updateAll should skip excluded plugins by default.- Single-plugin
/pp update <plugin> should still allow a deliberate manual update, or should require an explicit force flag if that is safer.
- The skipped plugins should be shown in updateAll output so operators understand why they were not updated.
Possible command surface
One of these would work:
/pp update ignore <plugin> and /pp update unignore <plugin>/pp pin <plugin> and /pp unpin <plugin>/pp updateAll --include-ignored for deliberate override
Implementation notes
- Store the setting with the local plugin tracking data, for example an
updateIgnored or pinned boolean on LocalPlugin.
- Preserve backwards compatibility with existing
plugins.json entries that do not include the new field.
- Filter ignored plugins before building the
/pp updateAll update plan.
- Keep the plugin visible in
/pp list, recognition, import/export, and manual update flows.
Summary
Add a per-plugin way to exclude selected plugins from
/pp updateAll, while keeping them tracked by Plugin Portal for listing, recognition, and manual updates.Credit to Zoriot for the report.
Problem
Some server owners need to hold back a specific plugin version even when newer marketplace versions exist. Today
/pp updateAllconsiders every tracked local plugin and has no per-plugin skip/pin mechanism. The only workaround is to stop tracking the plugin in Plugin Portal metadata, which is not ideal because it also loses normal Plugin Portal management context.A concrete example is a plugin releasing an update that breaks worlds or server behavior, where the owner still wants to update other plugins safely.
Proposed behavior
/pp updateAllshould skip excluded plugins by default./pp update <plugin>should still allow a deliberate manual update, or should require an explicit force flag if that is safer.Possible command surface
One of these would work:
/pp update ignore <plugin>and/pp update unignore <plugin>/pp pin <plugin>and/pp unpin <plugin>/pp updateAll --include-ignoredfor deliberate overrideImplementation notes
updateIgnoredorpinnedboolean onLocalPlugin.plugins.jsonentries that do not include the new field./pp updateAllupdate plan./pp list, recognition, import/export, and manual update flows.