The Wayback Machine - https://web.archive.org/web/20201104074915/https://github.com/pnpm/pnpm/issues/2706
Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Proper exit code from pnpm outdated #2706

Open
esatterwhite opened this issue Jul 24, 2020 · 1 comment
Open

Proper exit code from pnpm outdated #2706

esatterwhite opened this issue Jul 24, 2020 · 1 comment

Comments

@esatterwhite
Copy link

@esatterwhite esatterwhite commented Jul 24, 2020

pnpm version: 5.2.6

Code to reproduce the issue:

pnpm add [email protected]
pnpm outdated
echo $?
> 0

Expected behavior:

This command should return a non zero exit code if outdated dependencies are found.
Its pretty common to use the outdated command in CI to catch outdated dependencies at build time

Additionaly, it would be fantastic to be able to specify the severity of the dependency

npm oudated --severity=major # only error when deps are major versions behind

Actual behavior:

It always exits w/ 0

Additional information:

  • node -v prints: 12.18.1
  • Windows, OS X, or Linux?: linux
@zkochan zkochan self-assigned this Jul 27, 2020
zkochan added a commit that referenced this issue Jul 27, 2020
zkochan added a commit that referenced this issue Jul 27, 2020
`pnpm outdated` should exit with 1, when outdated found

`pnpm audit` should exit with 1 when issues are found

ref #2706
PR (#2718)
@zkochan
Copy link
Member

@zkochan zkochan commented Jul 27, 2020

The exit code issue fixed in 5.4.7 via #2718

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants
You can’t perform that action at this time.