{"version":"2.1.257","anchor":"artifact-asset-readspublishes-now-refuse-to-write-onto-a-bo","canonical_anchor":"artifact-asset-readspublishes-now-refuse-to-write-onto-a-bo","heading":"Artifact asset reads\/publishes now refuse to write onto a bound working copy","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.257\/e\/artifact-asset-readspublishes-now-refuse-to-write-onto-a-bo","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.257","markdown":"### Artifact asset reads\/publishes now refuse to write onto a bound working copy\n\nArtifact asset reads and publishes refuse to overwrite a bound working copy such as a synced git checkout.\n\nThe Artifact tool's `read_asset` and publish paths now check whether the target location is a bound or managed working copy, such as a synced git checkout, and refuse to save a fetched asset or publish onto it instead of silently overwriting it. The refusal surfaces as `asset_read_onto_working_copy`.\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5"}