-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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
fix: restore exit code on "npm outdated" #3799
Conversation
0e03826
to
c9cb522
Compare
Smoke test will have to be fixed for this. |
* More compact exitCode check * Update smoke-test to check exit code
@wraithgar: I've pushed a new commit to address the feedback. Smoke tests should be passing now. |
Not sure why this PR isn't showing as merged. It's in |
This will go out w/ Thursday's release. Thank you for submitting this fix! |
This change is wrong. Exit code 1 means the program had an error. Correctly listing outdated packages is not an error and must not return exit code 1. https://en.wikipedia.org/wiki/Exit_status "For the shell's purposes, a command which exits with a zero exit status has succeeded. A nonzero exit status indicates failure. " |
closes: #2556
ref: #1750
The xref'ed PR apparently dropped this behavior without any explanation.
release-latest
if appropriate.exitCode
andlogs
are somewhat related in terms of the expected results. I copy-pasted theexitCode
check everywhere for the time being.