Skip to content
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

Raise min. required Ruby version #4242

Closed
Garfield96 opened this issue Jul 15, 2023 · 3 comments
Closed

Raise min. required Ruby version #4242

Garfield96 opened this issue Jul 15, 2023 · 3 comments
Labels
enhancement Feature request or improve operations

Comments

@Garfield96
Copy link
Contributor

Is your feature request related to a problem? Please describe.

Currently, the minimum required Ruby version for Fluentd is 2.4, which reached EOL on 2020-03-31. The oldest Ruby version tested in CI runs is 2.7, which reached EOL on 2023-03-31. Supporting these versions not only endorses users to run outdated, potentially even vulnerable systems but also makes it difficult to use new language features (e.g. ractors).

Describe the solution you'd like

Drop support for Ruby 2.x or at least raise the min. required version to 2.7. In addition, the min. required version should not be based on arbitrary value, but instead, there should be a clear rule, like "Fluentd supports all maintained Ruby versions".

Describe alternatives you've considered

I don't think there is an alternative in the long run.

Additional context

Ruby version overview: https://www.ruby-lang.org/en/downloads/branches/

@daipom daipom added enhancement Feature request or improve operations and removed waiting-for-triage labels Jul 17, 2023
@daipom
Copy link
Contributor

daipom commented Jul 17, 2023

Thanks for your report!
The Fluent Package (we will change the name from td-agent), which we are about to release soon, will embed Ruby 3.
We also need to consider that min version in Fluentd itself.

gem.required_ruby_version = '>= 2.4'

@arminru
Copy link

arminru commented Dec 11, 2023

I think this has been addressed with #4288 so the issue could be closed.

@ashie ashie closed this as completed Dec 12, 2023
@ashie
Copy link
Member

ashie commented Dec 12, 2023

Fixed in #4288
Thanks for your report!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Feature request or improve operations
Projects
None yet
Development

No branches or pull requests

4 participants