{"version":"2.1.224","anchor":"a-plugin-entry-that-fails-validation-now-keeps-the-reason","canonical_anchor":"a-plugin-entry-that-fails-validation-now-keeps-the-reason","heading":"A plugin entry that fails validation now keeps the reason","tier":"notice","area":"Plugins","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224\/e\/a-plugin-entry-that-fails-validation-now-keeps-the-reason","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224","markdown":"### A plugin entry that fails validation now keeps the reason\n\nA marketplace entry with bad fields keeps its validation error instead of looking unsupported.\n\n**What**\n\nWhen a marketplace entry uses a source type Claude Code knows but gets its fields wrong, the entry is kept along with the validation error instead of looking identical to a source type this version simply does not recognize.\n\n**Details**\n\n- The message is compacted before storage: unrecognized field names are listed and sanitized, the text is truncated with an ellipsis, and extra items are rendered as \"(+N more)\".\n\n**Evidence**\n\n`Placeholder for source types this Claude Code version does not recognize, or a known type whose fields failed validation (then `error` `\n\n- Area: Plugins\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}