{"version":"2.1.283","anchor":"artifact-path-pin-checks-can-refuse-even-when-there-is-no-li","canonical_anchor":"artifact-path-pin-checks-can-refuse-even-when-there-is-no-li","heading":"Artifact publishing can refuse a stale file even when the file list is unavailable","tier":"notice","area":"Artifacts","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283\/e\/artifact-path-pin-checks-can-refuse-even-when-there-is-no-li","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283","markdown":"### Artifact publishing can refuse a stale file even when the file list is unavailable\n\nWhen the artifact file list can't be fetched, Claude Code no longer skips its file-change check and can still refuse a publish\n\n**Unclear.** It is not clear which switches control the artifact feature or who has it.\n\n**What**\n\nWhen publishing artifacts, Claude Code remembers the state of each file path from the file lists it has seen, and refuses to publish over a file that has changed since. Before, if the live file list could not be fetched, this check was skipped and the publish went ahead. Now:\n\n- files it already remembers as out of date are still refused\n\n- its memory of each file is updated from every file list it does see\n\n**Why**\n\nIt is harder to publish over an out-of-date file just because the file list happened to be unavailable.\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}