Under the hoodTier: how much it should matter to you
1Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
ArtifactsArea: what it touches
Internal ChangesKind: in v2.1.268,
Internal ChangesSection of the release
What
Previously, the list_files and read_file artifact actions produced a different error message when blocked by a read-permission deny rule than the verify and read actions did. Now all four actions route through the same shared error-handling logic, so a blocked read produces the same denial or target-changed message no matter which action triggered it.
Why
This makes the behavior consistent and predictable: whichever way an artifact read is blocked, the resulting error message is now the same across the board.
