task installed via npm always returns 0 exit code when build failed

[madconst]

Description

1. What I did: run task to build project. The project build failed (compilation error). Task printed 'Failed to run task "backend": exit status 2` in red.
2. What I expected: exit code ($? in bash) is non-zero.
3. What I got: exit code is 0.

The problem caused CI to not stop the build and erroneously continue with tests.

I have found that it is task installed via npm that always returns 0 exit code. It's easy to reproduce that, just add any command to the target that returns non-zero extit code. Then:

$ task
Failed to run task "backend": exit status 2
$ echo $?
0

If installing task via apt install, the exit code is correct (201).

Minimal working example:

version: '3'

tasks:
  default:
    cmds:
      - false

How to reproduce:

$ npm install -g @go-task/cli
$ ~/.nvm/versions/node/v24.10.0/bin/task # full path to ensure task from npm is used
$ echo $?
0
$ /usr/bin/task
$ echo $?
201

Version

3.45.5

Operating system

Linux (Ubuntu)

Experiments Enabled

No response

Example Taskfile

version: '3'

tasks:
  default:
    cmds:
      - false

[vmaerten]

This is fixed in Goreleaser but we wait for the next release