{"version":"2.1.248","anchor":"publishing-an-artifact-with-an-unreadable-file-reports-a-cle","canonical_anchor":"publishing-an-artifact-with-an-unreadable-file-reports-a-cle","heading":"Publishing an artifact with an unreadable file reports a clearer cause","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/publishing-an-artifact-with-an-unreadable-file-reports-a-cle","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Publishing an artifact with an unreadable file reports a clearer cause\n\nPublishing an artifact whose file can't be read now tells you that specifically.\n\n**What**\n\nWhen the artifact being published cannot be read and no favicon could be derived from its type, the tool now raises a specific unread-file error rather than a generic read failure.\n\n**Details**\n\n- The suggestion to start a new artifact from its type instead (passing `type_url`) is now only added when a favicon source was actually resolved\n- The old standalone \"favicon required to publish\" check is folded into the required-fields check, which reports that file path and favicon are both required\n\n**Evidence**\n\n`file_path and favicon are required to publish`\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}