Bump development local Ruby version from 3.3.1 to 3.4.8 #359
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.
What are you trying to accomplish?
Small gem maintenance fix to bring local development Ruby up to date. Somewhat unlikely folks have Ruby 3.3.1 installed at this point, meanwhile 3.4.8 is the latest and greatest. 🚀
https://www.ruby-lang.org/en/news/2025/12/17/ruby-3-4-8-released/
Note, there are some new console warnings re: literal string freezing and no-longer-automatically-included gems. For the former it appears we need to upgrade to at least v0.10.1 of the phonelib gem, of which we're currently on v0.8.7, re: the v0.10.1 release notes. For the latter we need to add the gems (ostruct, reline, reline, irb) to our Gemfile. Will do this in a follow-up PR.
What approach did you choose and why?
Standard practice.
What should reviewers focus on?
Is there any particular reason why we don't want to use latest Ruby in development? I can't think of a reason.
The impact of these changes
Better development experience especially for those coming to the repo fresh with modern Ruby.
Testing
Checklist
Determined not necessary as it's a developer facing change, not user facing.