{"version":"2.1.269","anchor":"new-currently-inert-validation-rejecting-auto-open-afte","canonical_anchor":"new-currently-inert-validation-rejecting-auto-open-afte","heading":"New (currently inert) validation rejecting auto_open: \"after_first_write\" combined with certain tool configuration","tier":"soon","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269\/e\/new-currently-inert-validation-rejecting-auto-open-afte","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269","markdown":"### New (currently inert) validation rejecting `auto_open: \"after_first_write\"` combined with certain tool configuration\n\nA new but currently inactive check would reject certain artifact publish configurations combining auto_open with specific tool settings\n\n**What**\n\nA new validation check was added to the code that publishes Artifacts. It's designed to reject a publish call that sets `auto_open: \"after_first_write\"` together with a certain tool configuration, returning an error. However, the helper function that's supposed to detect that tool configuration always returns false, so the check can never actually trigger right now.\n\n**Why**\n\nThis has no visible effect for users today since the check can never fire, but it signals a restriction on combining `auto_open: \"after_first_write\"` with certain tool settings that may become active in a future release.\n\n- Area: Artifacts\n- Names: `auto_open`\n- Tier: Nothing to try yet\n- Useful: 2\/5\n- Signal: 2\/5\n- Present in the build but not switched on"}