{"version":"2.1.239","anchor":"clearer-rules-for-force-publishing-an-artifact","canonical_anchor":"clearer-rules-for-force-publishing-an-artifact","heading":"Clearer rules for force-publishing an artifact","tier":"use","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239\/e\/clearer-rules-for-force-publishing-an-artifact","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239","markdown":"### Clearer rules for force-publishing an artifact\n\nThe force publish option now warns about in-page saves and says the server may refuse.\n\n**What**\n\nThe `force` option's description now covers the case where a newer version was saved from inside the artifact page itself, not just another session publishing, warns never to force purely to get past a conflict, and notes the server may refuse a force over an in-page save.\n\n**Details**\n\n- The client-side stale-version check that could abort a publish with `stale_version_guard` or `stale_version_guard_seeded` was removed from this path.\n- The read performed before publishing now passes session credentials.\n\n**Evidence**\n\n`unless it refuses force over a version saved from inside the page`\n\n- Area: Artifacts\n- Names: `force`\n- Tier: Use it now\n- Useful: 2\/5\n- Signal: 2\/5"}