{"version":"2.1.246","anchor":"artifact-data-files-need-a-known-file-type","canonical_anchor":"artifact-data-files-need-a-known-file-type","heading":"Artifact data files need a known file type","tier":"use","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246\/e\/artifact-data-files-need-a-known-file-type","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246","markdown":"### Artifact data files need a known file type\n\nPublishing an artifact data file with an unknown extension fails early and tells you to set contentType.\n\n**What**\n\nPublishing a data file with an artifact by path now fails up front if the file's extension has no known content type, and the error tells you to rename it to something recognised or list it under `files` in map form with an explicit `contentType`.\n\n**Details**\n\n- The error text suggests `.json` or `.txt` as known extensions.\n- Path resolution was reworked to try both the working directory and its real (symlink-resolved) path before computing the key the file is published under.\n\n**Evidence**\n\n`has no known content type for its extension \\u2014 rename it to a known one (e.g. .json or .txt)`\n\n- Area: Artifacts\n- Names: `contentType`, `files`\n- Tier: Use it now\n- Useful: 3\/5\n- Signal: 2\/5"}