Unblock bundle install on Ruby 4.0#35
Merged
Merged
Conversation
The gemspec declared `bundler "~> 2.4"` as a dev dependency, which collides with the Bundler that ships with Ruby 4.0 (currently 4.0.13) and stops `bundle install` cold. Bundler is required to install the gem in the first place, so declaring a version dependency on it as a dev dep is also redundant. Remove the line. Regenerate Gemfile.lock against Ruby 4.0.5. The previous lockfile pinned `stringio 3.1.0`, whose C extension uses the pre-4.0 signature for `rb_io_extract_modeenc` and fails to compile on 4.0. The refresh picks up Ruby-4-compatible versions across the dep tree (rails 8.1, psych 5.4, etc.). `bundle exec rake` passes (9 examples, 0 failures) on Ruby 4.0.5.
This was referenced Jun 22, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Build #3 went green on the bootstrap step but the test step failed because
bundle installcouldn't run on Ruby 4.0: the gemspec pinnedbundler "~> 2.4", and the lockfile pinnedstringio 3.1.0, whose C extension predates the 4.0rb_io_extract_modeencsignature change.What does this PR do?
spec.add_development_dependency "bundler", "~> 2.4"fromrequest_queue_time.gemspec. Bundler is required to install the gem in the first place, so declaring a version dependency on it as a dev dep is also redundant.Gemfile.lockagainst Ruby 4.0.5. The refresh moves the transitive dep tree forward (rails 8.1, psych 5.4, stringio 3.1.7, etc.) so native extensions build on Ruby 4.Note
Local
bundle exec rakeagainst Ruby 4.0.5 passes (9 examples, 0 failures). PR #33's tests will be 12 once this and #33 are both in.