You'll notice
Useful2 Signal2
Plugin updates blocked by org policy now fail early with a stated reason instead of quietly stalling.
What's wrong with this entry?
Anonymous. No account, no email.
What
A 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.
Details
- Update summary counters now include
marketplace_refresh_policy_skipped,plugins_helper_deferredandplugins_policy_blocked. - The CLI update wrapper now re-throws refusals across a wider family of failure codes, not only ones prefixed
command_source_.
Evidence
is blocked by your organization's policy and was not updated
Strings lifted out of the shipped bundle, so the claim above can be checked against them.