-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Change ruby version to 3.2.2 #21498
Change ruby version to 3.2.2 #21498
Conversation
📲 You can test the changes from this Pull Request in WordPress Alpha by scanning the QR code below to install the corresponding build.
|
📲 You can test the changes from this Pull Request in Jetpack Alpha by scanning the QR code below to install the corresponding build.
|
7662b12
to
69ef75b
Compare
69ef75b
to
17ec957
Compare
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.
I'm game for merging and addressing any Ruby issue that may arise.
I don't think it's worth trying to test them ahead of time, e.g. with a dummy release. I also think that, unless the issue turns out to be huge and expensive to fix, we'll be better off fixing them as soon as they come rather than reverting. Otherwise, we're only pushing the cost of fixing the issue to the future.
@mokagio Feel free to ping me if there is any issue 😃 |
17ec957 (#21498) switched the expected Ruby version to 3.x (🎉) Our Ruby linting automation only runs on diffed files so it didn't catch new violations that arose from the migration. The only reason I noticed, actually was because I just happened to modify the `Podfile` in 8df0aa0 (#21344) and got a CI failure.
17ec957 (#21498) switched the expected Ruby version to 3.x (🎉) Our Ruby linting automation only runs on diffed files so it didn't catch new violations that arose from the migration. The only reason I noticed, actually was because I just happened to modify the `Podfile` in 8df0aa0 (#21344) and got a CI failure.
17ec957 (#21498) switched the expected Ruby version to 3.x (🎉) Our Ruby linting automation only runs on diffed files so it didn't catch new violations that arose from the migration. The only reason I noticed, actually was because I just happened to modify the `Podfile` in 8df0aa0 (#21344) and got a CI failure.
Ruby 2.7.4 has reached end of life and it's about time that we migrate our Ruby toolings to Ruby 3.
Risk
The only risk I can see is there is a small chance that release tasks (that rely on release-toolkit) may break on Ruby 3, which we can't test at PR stage. But if that does happen and it's difficult to solve it properly, we can revert back to Ruby 2.7.4 by changing
.ruby-version
file (or revert the only comment in this PR).Regression Notes
N/A
PR submission checklist:
RELEASE-NOTES.txt
if necessary.UI Changes testing checklist: N/A