-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Tracking issue for errors resulting in a zero exit code #2932
Comments
watching |
I not only had it exit 0, but did not see any errors either - the output just stops early |
same here - commits are found, analyzeCommit step started but just exits with 0 not looking at any commits. Is there a way to pin conventional-changelog to an earlier version? |
An example in the other issue about this: While |
the latest betas of the commit-analyzer and release-notes-generator plugins have removed the use of promisify for the config loading process, which was the root cause of this for the situation where this was a problem related to #2929. thanks again for the investigation into this in semantic-release/commit-analyzer#525 (comment), @rvagg! we have seen some other reports of exiting zero when we shouldnt be in other contexts, so i'm going to keep this open for tracking those reports until we can dig deeper into those, but i think the preset related issue is solved once those plugins get promoted |
FYI I safely upgraded an initial package today to |
Current behavior
we've received reports of various errors resulting in a zero exit code when they would be expected to exit non-zero. some of these reports are related to the recent conventional-changelog preset breaking changes, but we have some previous reports as well.
i will gather the related issues as a follow up, but want to get this created to start pointing them to
Expected behavior
errors should result in a non-zero exit code so that it is clear when the release process fails
semantic-release
versionlatest
CI environment
various
Plugins used
No response
semantic-release
configurationn/a
CI logs
n/a
Related reports
The text was updated successfully, but these errors were encountered: