{"version":"2.1.222","anchor":"bad-metadata-in-frontmatter-and-manifests-now-warns","canonical_anchor":"bad-metadata-in-frontmatter-and-manifests-now-warns","heading":"Bad metadata in frontmatter and manifests now warns","tier":"use","area":"Plugins","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.222\/e\/bad-metadata-in-frontmatter-and-manifests-now-warns","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.222","markdown":"### Bad `metadata` in frontmatter and manifests now warns\n\nYou now get a warning when metadata in a skill, command, plugin or marketplace file is the wrong type.\n\n**What**\n\nAuthoring a skill, command, plugin manifest or marketplace entry with a non-object `metadata` value produces a validation warning instead of silent loss.\n\n**Details**\n\n- The warning names the type actually found and states that the value is dropped or ignored at load time.\n- Applies to skill and command frontmatter, plugin manifests, and marketplace plugin entries.\n\n**Evidence**\n\n`'metadata' must be a mapping (key: value pairs); got `\n\n- Area: Plugins\n- Names: `metadata`\n- Tier: Use it now\n- Useful: 3\/5\n- Signal: 0\/5"}