Plugin state updates — errors, warnings, needsRefresh, marketplace installation status, and applying a refresh — are now centralized in a dedicated store class with explicit methods (addErrors, addWarnings, markNeedsRefresh, setPendingMarketplaces, setMarketplaceStatus, applyRefresh), replacing inline state-object spreads in the plugin-refresh pipeline.
Plugin state management refactored into a dedicated store class
Plugin state management was consolidated into a dedicated store class.
Under the hoodTier: how much it should matter to you
2Useful: my rating, 1 to 5
0Signal: worth watching, 1 to 5
PluginsArea: what it touches
Internal ChangesKind: in v2.1.260,
Internal ChangesSection of the release