{"version":"2.1.271","anchor":"artifact-ref-resolution-now-tolerates-missing-read-version-f","canonical_anchor":"artifact-ref-resolution-now-tolerates-missing-read-version-f","heading":"Artifact ref resolution now tolerates missing read version for attached frames","tier":"internal","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271\/e\/artifact-ref-resolution-now-tolerates-missing-read-version-f","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271","markdown":"### Artifact ref resolution now tolerates missing read version for attached frames\n\nArtifact ref resolution no longer fails outright when a read version is missing for an attached frame\n\n**What**\n\nThe internal helper that resolves an artifact's current frame URL and version, used when cross-referencing artifact reads, used to return nothing whenever a read version was missing. Now it only returns nothing in that case if the matching frame's key doesn't start with the \"attached:\" prefix; otherwise it returns the reference without a version field.\n\n**Why**\n\nThis lets artifact references for attached frames still resolve even when no read version is recorded for them, instead of being dropped entirely.\n\n- Area: Artifacts\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}