Skip to content

gem: remove yajl-ruby from runtime dependencies for Ruby 4.1 - #5574

Merged
kenhys merged 1 commit into
fluent:masterfrom
Watson1978:remove-yajl-ruby-dependency
Oct 26, 2026
Merged

kenhys merged 1 commit into
fluent:masterfrom
Watson1978:remove-yajl-ruby-dependency

Conversation

@Watson1978

Copy link
Copy Markdown
Contributor

Which issue(s) this PR fixes:
Fixes #

What this PR does / why we need it:
The yajl-ruby dependency in fluentd.gemspec is guarded by RUBY_VERSION < "4.1", but the guard is evaluated only when the gem is built. So the published fluentd 1.20.0 gem always depends on yajl-ruby, and gem install fluentd fails on Ruby 4.1 because yajl-ruby cannot be built there. Fluentd itself no longer uses yajl-ruby since #5090 and #5383, so this PR removes the dependency.

Docs Changes:
N/A

Release Note:
gem: remove yajl-ruby from runtime dependencies to fix installation on Ruby 4.1. Plugins that require 'yajl' need to declare yajl-ruby in their own gemspec.

🤖 Generated with Claude Code

The Ruby version guard in the gemspec is evaluated only at gem build
time, so the published gem always depends on yajl-ruby. yajl-ruby
cannot be built on Ruby 4.1, so installing fluentd fails there.

Fluentd itself no longer uses yajl-ruby.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Signed-off-by: Shizuo Fujita <fujita@clear-code.com>
@Watson1978
Watson1978 force-pushed the remove-yajl-ruby-dependency branch from eb308e0 to 9cb7889 Compare October 26, 2026 02:03
@Watson1978 Watson1978 changed the title Fix gem installation failure on Ruby 4.1 gem: remove yajl-ruby from runtime dependencies for Ruby 4.1 Oct 26, 2026
@Watson1978
Watson1978 marked this pull request as ready for review October 26, 2026 02:39
@Watson1978
Watson1978 requested a review from kenhys October 26, 2026 02:39
@Watson1978 Watson1978 added this to the v1.20.1 milestone Oct 26, 2026
@kenhys
kenhys merged commit ca4c317 into fluent:master Oct 26, 2026
21 of 39 checks passed
@Watson1978

Copy link
Copy Markdown
Contributor Author

Thanks

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