{"version":"2.1.267","anchor":"artifact-republish-deadline-field-force-older-open-viewe","canonical_anchor":"artifact-republish-deadline-field-force-older-open-viewe","heading":"Artifact republish supports a 'deadline' to force old viewers to stop","tier":"use","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.267\/e\/artifact-republish-deadline-field-force-older-open-viewe","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.267","markdown":"### Artifact republish supports a 'deadline' to force old viewers to stop\n\nRepublishing an artifact can set a deadline telling older open copies of it when to stop, plus a reserved preflight.js hook\n\n**What**\n\n- Republishing an artifact now accepts an optional `deadline` value of `now`, `15m`, `1h`, `24h`, `7d`, or an ISO UTC timestamp, telling already-open older-version viewers of the artifact when they must stop. Published changes already reach open viewers automatically; this field is only for forcing old versions off. Multiple deadline declarations accumulate, and the earliest one wins.\n\n- The file name `preflight.js` at an artifact's root is now reserved: it runs against open pages when the artifact is published, and it must be an ES module of 8 KiB or less with a default-export function, or the publish is refused.\n\n**Why**\n\nThis lets a publisher forcibly retire stale open copies of a republished artifact instead of leaving them running indefinitely, and it reserves a hook point (`preflight.js`) for publish-time checks.\n\n- Area: Artifacts\n- Names: `deadline`\n- Tier: Use it now\n- Useful: 4\/5\n- Signal: 3\/5"}