{"version":"2.1.232","anchor":"allowedmarketplaces-works-as-an-alias-for-strictknownmarketp","canonical_anchor":"allowedmarketplaces-works-as-an-alias-for-strictknownmarketp","heading":"allowedMarketplaces works as an alias for strictKnownMarketplaces","tier":"use","area":"Managed Settings","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232\/e\/allowedmarketplaces-works-as-an-alias-for-strictknownmarketp","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232","markdown":"### `allowedMarketplaces` works as an alias for `strictKnownMarketplaces`\n\nManaged settings accept `allowedMarketplaces` for the marketplace allowlist; older clients still need the canonical key.\n\n**What**\n\nManaged settings can now spell the plugin marketplace allowlist as `allowedMarketplaces`, read exactly as `strictKnownMarketplaces`. If a file sets both, the alias is ignored and a warning is printed. Older Claude Code versions do not know the alias, so keep the canonical key when older clients read the same managed settings file.\n\n**Details**\n\n- The mapping is registered as a pair, `{ alias: \"allowedMarketplaces\", canonical: \"strictKnownMarketplaces\" }`.\n- Managed settings only; the alias is not read from user or project settings.\n\n**Evidence**\n\n`Alias for strictKnownMarketplaces (managed settings only): this key is read exactly as if it `\n\n- Area: Managed Settings\n- Names: `allowedMarketplaces`, `strictKnownMarketplaces`\n- Tier: Use it now\n- Useful: 2\/5\n- Signal: 1\/5"}