{"version":"2.1.238","anchor":"plugin-updates-blocked-by-org-policy-report-why-they-were-sk","canonical_anchor":"plugin-updates-blocked-by-org-policy-report-why-they-were-sk","heading":"Plugin updates blocked by org policy report why they were skipped","tier":"notice","area":"Plugins","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.238\/e\/plugin-updates-blocked-by-org-policy-report-why-they-were-sk","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.238","markdown":"### Plugin updates blocked by org policy report why they were skipped\n\nPlugin updates blocked by org policy now fail early with a stated reason instead of quietly stalling.\n\n**What**\n\nA plugin your organization's policy blocks now fails early with its own failure code, `plugin_policy_blocked`, and tells you it was not updated. A plugin held back by a version pin records a skip reason of `pinner_blocked` instead.\n\n**Details**\n\n- Update summary counters now include `marketplace_refresh_policy_skipped`, `plugins_helper_deferred` and `plugins_policy_blocked`.\n- The CLI update wrapper now re-throws refusals across a wider family of failure codes, not only ones prefixed `command_source_`.\n\n**Evidence**\n\n`is blocked by your organization's policy and was not updated`\n\n- Area: Plugins\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}