extraKnownMarketplaces now merges across settings files instead of one layer wiping the others.
What's wrong with this entry?
The extraKnownMarketplaces setting is now deep-merged across settings layers, so a project or managed-policy file can add a plugin marketplace without wiping out the ones defined at user or enterprise level.
- Both settings-merge paths were changed; previously the highest-precedence layer replaced the whole object.
extraKnownMarketplaces
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.224
Invalid
extraKnownMarketplacesentries are dropped with a warningBoth mention extra known marketplace
-
v2.1.232
additionalMarketplacessettings aliasBoth mention extra known marketplace
-
v2.1.223
Marketplace policy lists accept an owner wildcard
Both mention extra known marketplace