Improve gemfile - #2327
Merged
Merged
Improve gemfile#2327
Conversation
larouxn
force-pushed
the
improve_gemfile
branch
from
August 12, 2026 22:18
29b7f02 to
2195991
Compare
Collaborator
|
Thanks, @larouxn. LGTM 🚀 |
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.
Proposing we update the Gemfile to more obviously reflect that we're already using/support
minitest6.0+ (for Ruby 3.2+) andrubocop-minitest0.40+ and allow conditional usage ofpower_assert3.0+ on Ruby 3.2+ aspower_assert3.0 drops support for Ruby < 3.2 and we still support Ruby 3.0 and 3.1.Locally running: