You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am using npm-audit-resolver in a CI/CD Use Case with yarn berry and don't seem to get an exit code 1 back when there is an issue.
Expected behavior:
The expectation would be that as soon as an "unresolved issues found!" is detected, the exit code is 1 and not 0 as in the example.
Steps to reproduce:
In the example shown, there is already an audit-resolve.json file, so the output correctly shows "Total of 4 actions to process", but only one "modarate" issue is listed in the output. This is correct so far. Nevertheless, I would expect a 1 as the exit code here because an issue was found.
Here again the CI/CD pipeline use case:
with corresponding statement:
The text was updated successfully, but these errors were encountered:
I am using npm-audit-resolver in a CI/CD Use Case with yarn berry and don't seem to get an exit code 1 back when there is an issue.
Expected behavior:
The expectation would be that as soon as an "unresolved issues found!" is detected, the exit code is 1 and not 0 as in the example.
Steps to reproduce:
In the example shown, there is already an audit-resolve.json file, so the output correctly shows "Total of 4 actions to process", but only one "modarate" issue is listed in the output. This is correct so far. Nevertheless, I would expect a 1 as the exit code here because an issue was found.
Here again the CI/CD pipeline use case:
with corresponding statement:
The text was updated successfully, but these errors were encountered: