{"version":"2.1.287","anchor":"artifact-publish-rejects-mismatched-svg-copies","canonical_anchor":"artifact-publish-rejects-mismatched-svg-copies","heading":"Publishing an artifact now checks that SVG copies really are SVG images","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287\/e\/artifact-publish-rejects-mismatched-svg-copies","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287","markdown":"### Publishing an artifact now checks that SVG copies really are SVG images\n\nWhen publishing an artifact, a copy to or from a .svg name must be stored as an SVG image, and an SVG file can only be copied to a .svg name\n\n**What**\n\nWhen you publish an artifact (a file Claude Code shares for you), Claude Code now checks any copies involving SVG files more strictly. SVG is an image format for drawings and icons.\n\n- A file copied to or from a name ending in `.svg` must be stored as an SVG image.\n\n- A file stored as an SVG image may only be copied to a name ending in `.svg`.\n\nThe error message about files that cannot be copied has also been narrowed. It used to say a page, SVG or XML document cannot be copied. It now says a page or XML document cannot be copied, because SVG files are handled by the rules above.\n\n**Why**\n\nA publish that copies an SVG file under a mismatched name or type can now fail where it succeeded before. If a publish stops working, check that each `.svg` name holds an SVG image and that each SVG image keeps a `.svg` name.\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}