{"version":"2.1.238","anchor":"the-plugin-panel-explains-autoupdates-that-were-skipped-or-b","canonical_anchor":"the-plugin-panel-explains-autoupdates-that-were-skipped-or-b","heading":"The plugin panel explains autoupdates that were skipped or blocked","tier":"notice","area":"Plugins","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.238\/e\/the-plugin-panel-explains-autoupdates-that-were-skipped-or-b","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.238","markdown":"### The plugin panel explains autoupdates that were skipped or blocked\n\nThe plugin panel now explains updates skipped for a header command or blocked by policy.\n\n**What**\n\nTwo new plugin error states appear: one for an update skipped because it would have run a local header-minting command, and one for an update refused by managed policy. Both show their own message and offer no fix suggestion.\n\n**Details**\n\n- The internal names are `autoupdate-deferred-entry-helper` and `autoupdate-disabled-by-policy`.\n- The autoupdate notifier now dedupes and clears these per error rather than by comparing whole lists, so a repeated skip does not re-notify.\n- The log line now reads \"skipped (pinned, deferred or refused)\".\n\n**Evidence**\n\n`autoupdate-deferred-entry-helper`\n\n- Area: Plugins\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}