Repository navigation
Bump ci-queue to v0.102.0 - #439
Merged
Merged
Conversation
tekmaven
marked this pull request as ready for review
October 8, 2026 16:42
bmaynard
approved these changes
Oct 8, 2026
This branch was successfully deployed
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Bumps the Ruby gem version to 0.102.0.
Changes since v0.101.0:
No breaking changes to the API or the queue format. One behavior change: when
minitest-queue reportstops waiting while a lazy-load leader is still streaming tests (because--max-test-failedwas reached or the report timed out), it now prints the failures and exits with 44 or 43, as it does without lazy loading. It used to exit with 40 ("No leader was elected"). Runs where no leader starts still exit with 40.