{"version":"2.1.234","anchor":"clearer-and-stricter-checks-on-published-artifact-file-paths","canonical_anchor":"clearer-and-stricter-checks-on-published-artifact-file-paths","heading":"Clearer and stricter checks on published artifact file paths","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234\/e\/clearer-and-stricter-checks-on-published-artifact-file-paths","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234","markdown":"### Clearer and stricter checks on published artifact file paths\n\nInvalid file paths in a published artifact now name the actual problem instead of a generic error.\n\n**What**\n\nThe error for an invalid file path inside a published artifact now names the actual problem: an empty segment, a segment made only of dots and spaces, a path separator, a NUL byte, or a reserved name shape. Absolute paths that normalize into a reserved shape are rejected outright rather than accepted after normalization.\n\n**Evidence**\n\n`expected a non-empty array of segments, none empty or made only of dots and spaces, with no path separator, NUL or set-aside shape`\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}