Update to support minitest 6 plugin loading - #160
Merged
Conversation
bitwise-aiden
force-pushed
the
ba-update-minitest-6
branch
from
May 7, 2026 15:37
d25f861 to
7e50593
Compare
Contributor
Author
|
@rafaelfranca how do you feel about dropping 3.2 support since it's passed EOL? |
bitwise-aiden
force-pushed
the
ba-update-minitest-6
branch
from
May 7, 2026 15:55
ffcb8c1 to
7e50593
Compare
Member
|
Feel free to drop all EOL versions of Rails and Ruby. We already do. But let's do in another PR |
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.
December 2025 minitest released a new version that meant plugins weren't automatically discovered. This is causing issues in CI since it will automatically pull 6+ and we aren't manually loading when in this mode.
This adds a quick check and performs manual loading if necessary. Backwards compatible when minitest <6 is used.
Not explicitly bumping the Gemfile.lock so we can maintain full compatibility.
Depends on #161