Skip to content

Conversation

larouxn
Copy link

@larouxn larouxn commented Sep 16, 2025

Ruby 3.1 is EOL as of earlier this year (source) and as such we should probably drop support like #632 did for Ruby 3.0. Additionally this repo/gem's CI doesn't even test Ruby 3.1 anymore as of #653 from July 31st of this year. Thus, it's in fact a bit risky to still allow Ruby 3.1.

Inspired by #631

@kbrock
Copy link
Contributor

kbrock commented Sep 16, 2025

The bookworm (oldstable) release of Debian uses Ruby 3.1 as its default and it is supported until 2026.

Not saying that we have to support Debian, but I've been using Debian as a gauge for the gems that I support. (I don't run Debian, it was just brought up to me on another gem and the request seemed sound to me)

@larouxn
Copy link
Author

larouxn commented Sep 16, 2025

That's an interesting a fair point regarding Debian. While I would prefer to drop support for Ruby 3.1 as it's EOL, I am not a maintainer nor (yet) contributor to this gem so I'll leave it up to such people to decide.

That said, if we do intend to continue allowing Ruby 3.1 installs until 2026 we should add it back to CI.

ruby: ["3.4", "3.3", "3.2"]

@kbrock
Copy link
Contributor

kbrock commented Sep 17, 2025

Good point.

To be clear, I do not maintain this gem. (have contributed for 9 years)
That was just something I threw out there based upon comments given to me when I tried to drop older versions of ruby

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants