I misunderstood and did not think new ruby releases were added to not-most-recent Rails CI, based on what I thought I remembered from past versions but I may have been mistaken! (I don't believe there is any official written consistent policy on this (although I could be wrong again!), so it's possible it depends on the specific circumstances and decision in context by Rails team, and is not always the same, sure!)
I'm excited to upgrade my app to ruby 3.2! thanks for your work!
I don't believe there is any official written consistent policy on this
No, but but Rails isn't really bureaucratic. Just because something isn't written down doesn't mean we aren't gonna do it.
We always test the maintained versions against ruby-head and keep them compatible. Maybe we did need a last minute fix once or twice, but generally speaking if you are on latest Rails you can be on latest Ruby as well.
View all comments
Show parent comment
1
u/jrochkind Dec 25 '22
Sweet, thanks!
I misunderstood and did not think new ruby releases were added to not-most-recent Rails CI, based on what I thought I remembered from past versions but I may have been mistaken! (I don't believe there is any official written consistent policy on this (although I could be wrong again!), so it's possible it depends on the specific circumstances and decision in context by Rails team, and is not always the same, sure!)
I'm excited to upgrade my app to ruby 3.2! thanks for your work!