{"version":"2.1.248","anchor":"artifact-writes-can-skip-a-re-read-when-your-own-last-read-s","canonical_anchor":"artifact-writes-can-skip-a-re-read-when-your-own-last-read-s","heading":"Artifact writes can skip a re-read when your own last read saw the current version","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/artifact-writes-can-skip-a-re-read-when-your-own-last-read-s","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Artifact writes can skip a re-read when your own last read saw the current version\n\nPublishing an artifact skips its re-read check when your last read matched the live version.\n\n**What**\n\nPublishing an artifact normally re-reads the live page to check nobody else changed it. That round trip is now skipped when the publish is your own and your recorded read already matched the live version with no other observers. On by default; a server override can turn it off.\n\n**Details**\n\n- Gated on `tengu_cobalt_plinth_teasel`, whose compiled fallback is on.\n- The skip path returns `reason: \"proceed_own_version\"` and emits `artifact_guard_autoread` with `mode: proceed_own_version`.\n\n**Evidence**\n\n`tengu_cobalt_plinth_teasel`\n\n- Flag `tengu_cobalt_plinth_teasel`: Not enough to say (read for one account on one subscription tier against v2.1.248; this account: no value returned, anonymous baseline: no value returned, compiled default: on)\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}