{"version":"2.1.219","anchor":"republishing-an-artifact-page-now-verifies-it-came-from-this","canonical_anchor":"republishing-an-artifact-page-now-verifies-it-came-from-this","heading":"Republishing an artifact page now verifies it came from this CLI build","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.219\/e\/republishing-an-artifact-page-now-verifies-it-came-from-this","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.219","markdown":"### Republishing an artifact page now verifies it came from this CLI build\n\nRepublishing an artifact page fails if it was built by a different CLI version; re-run the command.\n\n**What**\n\nRepublish checks the stored page against this build's template and refuses when they have drifted, instead of pushing a page assembled by a different CLI version.\n\n**Details**\n\n- Pinned markup fragments, script hashes, an inline blind-spots style allowlist and the diagram runtime must all match\n- On mismatch the republish fails with `pr_review_republish_template_drift` and advises re-running `\/artifact-pr-review`\n- A separate new failure, `pr_review_republish_mermaid_unavailable`, covers a page carrying a diagram runtime this CLI could not load\n\n**Evidence**\n\n`pr_review_republish_template_drift`\n\n- Area: Artifacts\n- Names: `\/artifact-pr-review`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 0\/5"}