{"version":"2.1.267","anchor":"artifact-file-uploads-now-reject-replacement-characterunpai","canonical_anchor":"artifact-file-uploads-now-reject-replacement-characterunpai","heading":"Artifact file uploads now reject replacement-character\/unpaired-surrogate text","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.267\/e\/artifact-file-uploads-now-reject-replacement-characterunpai","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.267","markdown":"### Artifact file uploads now reject replacement-character\/unpaired-surrogate text\n\nArtifact text file uploads are now rejected if they contain the Unicode replacement character or an unpaired surrogate\n\n**What**\n\nWhen a text-type file is validated for publishing to an Artifact, content containing the Unicode replacement character (U+FFFD, the symbol that appears when text can't be decoded properly) or an unpaired surrogate (a broken piece of a multi-part character) is now rejected with a specific error. For HTML files, the error also explains that the character should be escaped as `�` instead.\n\n**Why**\n\nThis catches text corruption before it's published, rather than letting broken or unreadable characters make it into a live artifact.\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}