A workflow whose script sits outside your readable paths is now denied outright.
What's wrong with this entry?
If a workflow's script file sits outside the set of paths the session is allowed to read, the tool now denies the call outright instead of quietly carrying on.
- The denial happens in the workflow tool's permission check, so it is reported as a permission failure rather than a missing file.
workflow scriptPath outside the readable set
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.239
Workflow tool gains run operations, with the auto-approval hook switched off
Both mention workflow
-
v2.1.239
Workflow tool has a second command shape built in but switched off
Both mention workflow
-
v2.1.239
Workflow "v2 run" handles are scaffolded but never created
Both mention workflow