-
Notifications
You must be signed in to change notification settings - Fork 127
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
πΌ Update CI matrix Ruby versions #880
Conversation
I think 2.6 shouldn't be removed because it's still supported by this gem. EOL of a version only means the version itself won't receive further updates (usually), but it doesn't mean gems have dropped support for it. |
@st0012 My understanding is that Ruby 2.6 is no longer receiving any updates anymore and Ruby 2.7 is soon to enter EOL state and enter a similar condition. I'm going off of the info on https://www.ruby-lang.org/en/downloads/ though, which states that Ruby 2.6.10 is not maintained anymore and 2.7.x is soon to enter the same state. On a side note I think the 3.2 support here may be causing some of the tests to fail as it seems we are returning objects that aren't the types we are expecting; this may require some further investigation and code updates. |
@gwillcox-r7 As I've said, a version of Ruby stop receiving updates != gems will drop support of it right away. Given that Ruby 2.6 is still supported by this particular gem, it's better to make sure it's tested on CI as well. |
Sorry for late reply, and I've understood that it is necessary to leave Ruby 2.6. Is it ok to add Ruby 3.2? |
Of course, other libs like |
cc @ko1 I think this could help distinguish if failures are caused by Ruby 3.2 and/or 3.3. |
Thank you for the patch and discussion.
If you find any trouble on Ruby 2.6 on CI, please tell me and drop it. |
(in other words) we shouldn't hesitate to introduce 2.6 incompatible code on debug.gem just now. |
Description
Update CI matrix ruby versions.
Remove 2.6π₯ref: https://www.ruby-lang.org/en/downloads/branches/