{"version":"2.1.242","anchor":"artifact-publish-recognises-removal-only-calls-and-explains-","canonical_anchor":"artifact-publish-recognises-removal-only-calls-and-explains-","heading":"Artifact publish recognises removal-only calls and explains duplicate paths","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242\/e\/artifact-publish-recognises-removal-only-calls-and-explains-","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242","markdown":"### Artifact publish recognises removal-only calls and explains duplicate paths\n\nArtifact updates that only remove files now count as a publish and go through.\n\n**What**\n\nA call now counts as a publish when it only removes files or only sets live files, not just when it lists files to upload, so removal-only updates go through.\n\n**Details**\n\n- The duplicate-path error was rewritten from a terse note into an instruction naming the repeated path.\n- Publish responses carry a marker for an artifact that is gone and a flag for a 403 caused by the artifact belonging to another organisation.\n\n**Evidence**\n\n`is listed more than once in`\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}