npm-outdated job don't allow failure anymore since version 3.0.0

Describe the bug

In version 2.4.0 having outdated modules leads to a warning, not a pipeline failure. Indeed, outdated modules are not a problem, but it's just better to know. In version 3.0.0 having outdated modules leads to a pipeline failure.

Expected behavior

The npm-outdated job should allow failure

Actual behavior

In version 3.0.0 of the template, having outdated modules leads to a pipeline failure.

Logs and/or screenshots

(Join any relevant logs and/or screenshot. Please use code blocks (```) to format console output, logs, and code.)

Context & Configuration

Link to a project, pipeline or job facing the bug: (please provide one if possible)

The issue was reproduced using:

  • Version of the template: 3.0.0
  • GitLab server(s): (Was it gitlab.com? A self-managed server? Which version? CE / EE? Which license?)
  • GitLab runner(s): (type in any relevant information about the GitLab runner(s) you used)

Here is the .gitlab-ci.yml file:

# Add your .gitlab-ci.yml here, if applicable and useful.

(If useful, list configured GitLab CI project and/or group variables.)

Configured GitLab CI project or group variables:

  • VARIABLE_1
  • VARIABLE_2
  • ...

(Finally add any possible additional useful context info here.)