You can now write additionalMarketplaces and allowedMarketplaces as aliases for the older marketplace settings keys.
What's wrong with this entry?
Settings files can now write additionalMarketplaces for extraKnownMarketplaces and allowedMarketplaces for strictKnownMarketplaces. The alias is folded into the canonical key when settings are read, and if both spellings appear in one file the alias is ignored with a warning.
- Applied on the normal settings read path, the raw-settings fallback path, and the settings write path, so Claude Code may rewrite an alias to the canonical spelling when it saves.
- The warning names both keys: keep only the canonical one.
- The aliases were also added to the list of keys the SDK strips when sanitizing settings, alongside
enabledPluginsandextraKnownMarketplaces.
are the same setting; keep only, "${e.alias}" and "${e.canonical}" are the same setting; keep only "${e.canonical}"
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.223
Marketplace policy lists accept an owner wildcard
Both mention marketplace extra known strict
-
v2.1.224
Invalid
extraKnownMarketplacesentries are dropped with a warningBoth mention marketplace extra known
-
v2.1.228
extraKnownMarketplaces merges instead of being replaced
Both mention marketplace extra known