{"version":"2.1.274","anchor":"artifact-create-now-accepts-per-file-content-type","canonical_anchor":"artifact-create-now-accepts-per-file-content-type","heading":"Artifact and skill publishing can now set a content type per file","tier":"use","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.274\/e\/artifact-create-now-accepts-per-file-content-type","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.274","markdown":"### Artifact and skill publishing can now set a content type per file\n\nArtifact and skill file entries can now be an object specifying a source path and content type, not just a plain path string\n\n**What**\n\nWhen creating or publishing an Artifact or Skill, the `files` map used to only accept a plain path string for each file. It now also accepts an object with a `from` field (the source path) and a `contentType` field, letting a publish call specify a MIME\/content type per uploaded file instead of only where it comes from.\n\nThe internal handler that admits these files, checking things like path traversal and size limits, was updated to read the source path from `from` when a file entry uses this new object form, rather than assuming it's always a bare string.\n\n**Why**\n\nThis lets publishers control the content type of individual uploaded files (for example, forcing a file to be treated as plain text or a specific format) rather than relying on automatic detection.\n\n- Area: Artifacts\n- Names: `contentType`\n- Tier: Use it now\n- Useful: 3\/5\n- Signal: 1\/5"}