FleekDash 2.6.3 introduces controlled plugin update governance for teams that value release stability over update speed. You can lock plugins to a chosen version, suppress update prompts for pinned packages, and roll out policy globally or by role.
What's New
Version locking for plugins: pin a plugin at a specific version so FleekDash keeps it fixed instead of auto-updating on every new upstream release.
No forced noise for pinned plugins: when a plugin is intentionally locked, update alerts for that package can be suppressed so operators are not spammed with "update now" prompts they cannot act on.
Policy scope control (global or by role): apply update-lock behavior platform-wide or restrict/allow by role so each team works under the right governance model.
Stable-only updates opt-in: FleekDash can be configured to prefer more stable update tracks, helping teams avoid early churn from fast-moving plugin releases.
What's Improved
Safer release operations: agencies and enterprise admins can hold production on known-good plugin versions while validating new releases on staging first.
Cleaner update workflow: fewer reactive updates and fewer false-priority alerts, with explicit policy that matches each team's risk tolerance.
