{"version":"2.1.232","anchor":"artifact-publishing-now-strips-every-head-block-not-just-the","canonical_anchor":"artifact-publishing-now-strips-every-head-block-not-just-the","heading":"Artifact publishing now strips every head block, not just the first","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232\/e\/artifact-publishing-now-strips-every-head-block-not-just-the","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232","markdown":"### Artifact publishing now strips every head block, not just the first\n\nPublishing an artifact now strips every head block, not just the first one.\n\n**What**\n\nThe cleanup that runs before an artifact is published used to remove a single matching head block. It now loops until none remain, splicing them all out and counting the total removed bytes against the size limit, before the base href and frame-runtime attribute are stripped.\n\n**Evidence**\n\n`data-frame-runtime=`\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}