Pin power_assert to v2 for Ruby 2.7 (v3 requires 3.1+) #1135
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
tompng
approved these changes
Nov 5, 2025
eregon
added a commit
to eregon/psych
that referenced
this pull request
Nov 5, 2025
* See ruby/power_assert#61 * Same approach as ruby/irb#1135
ima1zumi
added a commit
that referenced
this pull request
Nov 7, 2025
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.
The CI build is failing on Ruby 2.7 because power_assert v3.0.0 dropped support for Ruby versions below 3.1.
While we should probably consider dropping support for Ruby 2.7 soon, this PR prioritizes restoring the CI build. It pins the power_assert version for Ruby 2.7.
Since the CI is still passing on Ruby 3.0, this version constraint is applied only to Ruby 2.7.
required_ruby_versionto be Ruby 3.1 power_assert#61