{"version":"2.1.285","anchor":"artifact-publish-validation-rejects-and-consolidates-file-l","canonical_anchor":"artifact-publish-validation-rejects-and-consolidates-file-l","heading":"Workshop pages now explain why a <select> dropdown is rejected","tier":"notice","area":"Elsewhere","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285\/e\/artifact-publish-validation-rejects-and-consolidates-file-l","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285","markdown":"### Workshop pages now explain why a <select> dropdown is rejected\n\nPublishing a workshop page with a element now fails with a specific explanation and a suggested alternative\n\n**What**\n\nWhen you publish a workshop page, Claude Code checks its markup first. A `<select>` element (a dropdown menu) now fails that check with its own message: browsers and the checker read what is inside a dropdown differently, so markup inside it would not be inspected. The message suggests building the control from a list or buttons instead. Before, a `<select>` got only the general \"is not allowed on a workshop page\" message.\n\nThe checks on how many files a publish contains and where they sit were also merged into shared code, so the same checks now run whether or not the publish specifies a type.\n\n**Why**\n\nIf a page uses a dropdown, the error now tells you why and what to use instead, rather than a bare refusal.\n\n- Area: Elsewhere\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}