Drop support for RSpec 3.5–3.7 #121
Merged
Conversation
This file contains 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
dan-manges
force-pushed
the
dan/drop-support
branch
from
cc96d17
to
2885df0
Compare
TAGraves
approved these changes
Feb 19, 2024
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.
#120 revealed that RSpec 3.5–3.7 is not compatible with Ruby 3.2+. RSpec 3.7 is six years old, so we're going to drop support for it. I'm making these changes in preparation for adding support for RSpec 3.13.
Ruby 3.2 was released on 2022-12-25
RSpec 3.7 was released on 2018-01-03
And RSpec 3.5 was released on 2016-07-01