fix(ci): don't cancel other update dependencies tasks when one fails #7601
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
gribnoysup
added
no release notes
kraenhansen
approved these changes
Nov 26, 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.
Updating mongosh to latest currently fails causing all the other dependency update tasks to fail, we don't want that to happen. If I got it right how continue-on-error works, setting this option to
trueshould do the trick: it would not abort other jobs in the group, but will at the end show the job as failed, that way we both get signals that something goes wrong and update what can be updatedTo be clear, this is not a fix that will deal with monoghs updates, seems like we need a better strategy to pull related dependencies there, "all to latest" doesn't really work there