-
Notifications
You must be signed in to change notification settings - Fork 225
Remove support for Ruby 3.1 and aligned JRuby 9.4. Add support for JRuby 10. #514
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
base: main
Are you sure you want to change the base?
Conversation
The JRuby failures make me think that in practice this PR needs to land on top of #508. |
e290fa9
to
1a16b19
Compare
e5a99e2
to
150583b
Compare
|
Note that this includes some of the JRuby support fixes from #508. |
This could probably use more review than "we finally got CI to pass." |
…r JRuby 10 - rubycritic.gemspec: update minimum Ruby version to 3.2 - .rubocop.yml: update target Ruby version to 3.2 - CI: drop Ruby 3.1, and change jruby from 9.4 (Ruby 3.1) to jruby to 10 (Ruby 3.4) - add platform value to the gemspec, and require jar-dependencies version # Conflicts: # CHANGELOG.md
This patch only differs from the prior attempt in that the CHANGELOG was updated. This failure is the same failure as from two runs ago. I do not see it on my machine. I could use help investigating. |
I can now intermittently reproduce this failure locally. |
Per https://endoflife.date/ruby, Ruby 3.1 is EOL. This PR prepares for when we want to drop support.
Note: this PR changes the JRuby CI tests from 9.4 (Ruby 3.1) to HEAD (Ruby 3.4, still in testing), because there isn't a post-9.4 stable JRuby with a newer Ruby version. I expect we'll want to change the CI again once one is available.
continue-on-error
Check list: