馃挜 Drop ruby 2.7 and 3.0 support, and require 3.1 #276
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
|
@shugo @hsbt Are you okay with bumping the minimum ruby version for the 0.5.x releases? As a policy, I'd like to only change the minimum required ruby when we bump our |
nevans
force-pushed
the
require-ruby-3.1
branch
2 times, most recently
from
1cf80d7
to
979d82f
Compare
Ruby 2.7 EOL was 2023-03-31. Ruby 3.0 EOL was 2024-04-23. Currently, net-imap remains compatible with ruby 2.7. But some of my unmerged branches do use ruby 3.1 syntax (e.g: updated pattern matching and endless method definitions). It will be nice if I don't need to update those branches for compatibility with EOL rubies. ---- _**NOTE:** The next release after this is merged should be v0.5.0._
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.
Ruby 2.7 EOL was 2023-03-31.
Ruby 3.0 EOL was 2024-04-23.
Currently, net-imap remains compatible with ruby 2.7. But some of my unmerged branches do use ruby 3.1 syntax (e.g: updated pattern matching and endless method definitions). It will be nice if I don't need to update those branches for compatibility with EOL rubies.
NOTE: The next release after this is merged should be v0.5.0.