{"version":"2.1.248","anchor":"published-page-markup-parser-no-longer-shares-regex-state-be","canonical_anchor":"published-page-markup-parser-no-longer-shares-regex-state-be","heading":"Published-page markup parser no longer shares regex state between parses","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/published-page-markup-parser-no-longer-shares-regex-state-be","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Published-page markup parser no longer shares regex state between parses\n\nTwo published artifact pages parsed at once can no longer corrupt each other's validation.\n\n**What**\n\nThe parser that decides what markup a published artifact page may contain now builds its matching state fresh per call, closing a class of bug where two parses running together could corrupt each other's position. What is accepted is unchanged: a doctype, the same base href shape, utf-8 charset only, and the expected root mount element.\n\n**Evidence**\n\n`<!doctype[ \\t\\n\\f\\r]+html[ \\t\\n\\f\\r]*>`\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}