Skip to content

Conversation

@ViTrex96
Copy link

@ViTrex96 ViTrex96 commented Dec 4, 2025

Hi! 👋
I noticed that this command was returning an exit code of 1 even when it completed successfully. This caused some unexpected behavior with monitoring tools such as Sentry cron monitoring which rely on the commands exit code to decide whether to trigger their onSuccess or onFailure handlers. Because of the non-zero exit code, these systems interpreted successful runs as failures and sent incorrect failure check-ins.

This PR updates the command to return 0 on success, following the standard exit-code conventions. It’s a small change, but I thought it would be a nice improvement to help avoid misleading error reports in setups that monitor exit codes.

Thanks for maintaining this package! 🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant