{"version":"2.1.248","anchor":"publishing-re-checks-the-server-for-a-comment-room-before-sk","canonical_anchor":"publishing-re-checks-the-server-for-a-comment-room-before-sk","heading":"Publishing re-checks the server for a comment room before skipping one","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/publishing-re-checks-the-server-for-a-comment-room-before-sk","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Publishing re-checks the server for a comment room before skipping one\n\nPublishing checks the server for comment-room support before skipping it.\n\n**What**\n\nWhen a published artifact does not locally look like it has a comment room but was created from a type with the room setting on, publish now asks the server for the artifact's capabilities before deciding, instead of trusting only local knowledge.\n\n**Details**\n\n- If that read fails or comes back empty, the reported room status is the existing skip reason, or the new value `unread` when there is none.\n- Still inside the existing room consent and schema checks; no new flag.\n\n**Evidence**\n\n`zt.artifactRoomSkipReason(ee) ?? \"unread\"`\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5"}