Drop rails <6.0 #689
Drop rails <6.0 #689
Conversation
kbrock
force-pushed
the
ruby_version
branch
6 times, most recently
from
4718382 to
6bac04a
Compare
It's still pinned & supported in Debian (link may timeout, packages site can be overloaded), meaning it's still maintained until at least 2026-06-10 and people who follow current Debian will be "stuck" until the freeze completes and Trixie is released, after which people can update to rails 7.2.2. Supporting Debian may not be in the interest of this project, but I merely wanted to point out that EOL @ Rails Foundation does not mean EOL in reality. |
|
@SleeplessByte Thanks. I knew there was a reason I hadn't merged this yet. You proposing keeping 6.1. Opinion on 6.0 regards to Debian? |
|
Personally I keep my gems working on stable Debian but not maintenance Debian. So at this point I have dropped 6.0 even though on Debian it still gets security fixes. I'm just one person 😁 |
|
Also, if we drop 6.x in master, i'm not adverse to maintaining a stable branch for older bug fixes. The changes I want to make should be compatible for rails 5.x-8.x, but the internals have changed a bit around the way that scopes work, so this has been tricky. |
|
That would be fine with me tbh. Goed beyond what many gem maintainers do. |
fixup
2 participants
Not sure if we want to drop older rubies
rails 6.0 doesn't support ruby 3.0, so dropping 6.0 simplifies the matrix. It was EOL 2023
rails 6.1 was EOL 2024. I'm open to adding this back if someone needs, but the 7.0 code base changes a lot in the internals that we may want to follow.