{"version":"2.1.228","anchor":"plugin-installs-can-fail-closed-on-unreadable-marketplace-so","canonical_anchor":"plugin-installs-can-fail-closed-on-unreadable-marketplace-so","heading":"Plugin installs can fail closed on unreadable marketplace sources","tier":"notice","area":"Plugins","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.228\/e\/plugin-installs-can-fail-closed-on-unreadable-marketplace-so","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.228","markdown":"### Plugin installs can fail closed on unreadable marketplace sources\n\nPlugin installs can now be blocked outright when a marketplace source can't be read.\n\n**What**\n\nResolving which marketplace a plugin dependency comes from gained a fail-closed option. When the list of known marketplaces comes back empty, an unresolvable marketplace is treated as blocked rather than quietly allowed, which can turn an install that used to succeed into a policy block.\n\n**Details**\n\n- The option is `failClosedOnUnknownSource`; the block is reported as `marketplace-blocked-by-policy`.\n- It only applies when managed plugin policy sources are present. Without them the old permissive behaviour stands.\n\n**Evidence**\n\n`failClosedOnUnknownSource`\n\n- Area: Plugins\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5"}