Seems like `pipefail` is not applied to `status` commands

[arikkfir]

Description

Taskfile:

version '3'

set:
  - errexit
  - nounset
  - pipefail
  - xtrace

...
  foo:
    cmd: echo RUNNING FOO
    status:
      - cat non-existent-file | jq '{}'
...

Running this:

$ task foo
task: Task "foo" is up to date

As a user, I expected pipefail to be applied and used for status commands as well, not just for cmd/cmds.

Version

3.45.4

Operating system

macOS

Experiments Enabled

No response

Example Taskfile

version '3'

set:
  - errexit
  - nounset
  - pipefail
  - xtrace

tasks:
  foo:
    cmd: echo RUNNING FOO
    status:
      - cat non-existent-file | jq '{}'

[trulede]

@arikkfir Hi, I developed a draft PR for this. You might evaluate it and provide feedback, if it works as you expect (or not).

You can also not do this at all, and formulate your task like this:

version '3'

tasks:
  foo:
    cmd: echo RUNNING FOO
    status:
      - cat non-existent-file
      - jq '{}'

Which I think achieves the same effect.

[arikkfir]

Well, it would achieve the same effect for my dummy example, sure. But in real-world scenario, you would have some cURL call piped into a yq or jq pipe, or even more elaborate pipes - and splitting those is kind of a bummer :)

(otherwise, each section in the pipeline would need to write to a file, and the next one would need to read from the file, and so on...)

[trulede]

@arikkfir and the PR is there, if you are capable, you might like to try it and provide feedback (about if the PR).