You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
ArtifactsArea: what it touches
Bug FixesKind: in v2.1.248,
Bug FixesSection of the release
What
When 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.
Details
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
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
Evidence
file_path and favicon are required to publish
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
