Marketplace validation errors now name the bad source and tell you how to fix it.
What's wrong with this entry?
A bare plugin source in a marketplace file now fails with a message naming the source and telling you to either use a ./relative/path or set metadata.pluginRoot. Reserved plugin names are also checked against a single table now instead of one rule per name.
- Reserved names covered by the table:
inline,builtinandskills-dir. - Full message:
Bare source name "${b}" requires metadata.pluginRoot. Use "./relative/path", or set metadata.pluginRoot (e.g. "./plugins") to allow bare names.
Bare source name "${b}" requires metadata.pluginRoot. Use "./relative/path", or set metadata.pluginRoot (e.g. "./plugins") to allow bare names.
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.246
Hook and command paths can start with $CLAUDE_PLUGIN_ROOT
Both mention root
-
v2.1.222
Commands, skills and plugin manifests accept a free-form metadata object
Both mention metadata
-
v2.1.222
Bad
metadatain frontmatter and manifests now warnsBoth mention metadata