You might think too conservative approach, we do not want to change adopted ruby version to ruby 3.3 for latest v1.17 container images.
So, these kind of change will be merged when (next) v1.18 container image is ready for release.
(Fluentd v1.18 or later will be shipped for next fluent-package v6 LTS)
Thanks for feedback.
You might think too conservative approach, we do not want to change adopted ruby version to ruby 3.3 for latest v1.17 container images.
So, these kind of change will be merged when (next) v1.18 container image is ready for release. (Fluentd v1.18 or later will be shipped for next fluent-package v6 LTS)
Mark as pending for a while.