-
Notifications
You must be signed in to change notification settings - Fork 29
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
💥 Drop ruby 2.7 and 3.0 support, and require 3.1 #276
Conversation
@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 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That sounds reasonable 👍
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👌
1cf80d7
to
979d82f
Compare
b86789f
to
b14a63d
Compare
The next release from the main branch will be 0.5.0.
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._
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.