{"version":"2.1.228","anchor":"published-artifact-bundles-rejected-when-they-contain-frame-","canonical_anchor":"published-artifact-bundles-rejected-when-they-contain-frame-","heading":"Published artifact bundles rejected when they contain frame-runtime markers","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.228\/e\/published-artifact-bundles-rejected-when-they-contain-frame-","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.228","markdown":"### Published artifact bundles rejected when they contain frame-runtime markers\n\nArtifact bundles containing frame-runtime markers are now refused at publish time.\n\n**What**\n\nThe check that runs before an artifact bundle is published now also refuses bundles containing `<!-- frame-runtime -->` and `<!-- \/frame-runtime -->` markers, joining the existing refusals for mermaid and chart-runtime markers.\n\n**Details**\n\n- Rejection message: `bundle contains a frame-runtime serve sentinel`.\n\n**Evidence**\n\n`bundle contains a frame-runtime serve sentinel`\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5"}