Return non-zero exit code when scan report data is not healthy. #986
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![graphite-app[bot]](https://avatars.githubusercontent.com/in/158384?s=60&v=4){kind=small}
graydonhope
force-pushed
the
unhealthy-report-exit-code
branch
2 times, most recently
from
e858d15 to
9e98037
Compare
jdalton
previously approved these changes
Dec 19, 2025
jdalton
requested changes
Dec 19, 2025
Contributor
jdalton
left a comment
jdalton
left a comment
There was a problem hiding this comment.
@graydonhope Please implement this against the v1.x branch.
…king alerts were found. This is the expected behaviour based on our docs: https://docs.socket.dev/docs/socket-ci#non-zero-exit-code
graydonhope
force-pushed
the
unhealthy-report-exit-code
branch
from
9e98037 to
c4bcc5c
Compare
jdalton
approved these changes
Dec 19, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes the issue where socket ci would exit with code 0 even when
blocking alerts were found.
This is the expected behaviour based on our docs: https://docs.socket.dev/docs/socket-ci#non-zero-exit-code