What probably matters to youSection of the release
What
A new managed settings key, disableCommandPluginSources, stops plugins that come from a command source from being installed, updated or re-resolved. If it is unset it follows allowManagedHooksOnly, so an organization that already restricts hooks gets this too. Either key blocking produces a dedicated message naming both keys. Both fall back to blocking when the configured value fails validation. Only read from managed settings, so absent those, command sources stay allowed.
When blocked, the plugin is not installed or updated and its command is not run.
Evidence
Command-sourced plugins are disabled by your organization's managed settings (disableCommandPluginSources / allowManagedHooksOnly). The plugin was not installed or updated and its command was not run.
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
