Raise minimum Ruby to 3.1; CI now covers 3.1-3.5 + head#7
Merged
Conversation
Drops Ruby 3.0 (EOL since March 2024, no upstream security patches) from required_ruby_version, the CI matrix, and rubocop's TargetRubyVersion. The matrix now spans 3.1, 3.2, 3.3, 3.4, 3.5, plus `head` (4.0 development branch) as a continue-on-error early-warning smoke test. Bumping TargetRubyVersion to 3.1 unlocked Naming/BlockForwarding and Style/ArgumentsForwarding, which surfaced `&block` patterns in Services::CommandHandle. Replaced with the anonymous form (`&`). This is a breaking change for anyone still running on Ruby 3.0 — the next release should be 0.4.0 rather than 0.3.6. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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.
Summary
Drops Ruby 3.0 (EOL since March 2024) from the supported floor and expands the CI matrix forward.
required_ruby_version→>= 3.1.0(was>= 3.0.0)TargetRubyVersionin.rubocop.yml→3.13.1, 3.2, 3.3, 3.4, 3.5, headheadtracks Ruby's main branch (currently 4.0 development) and runs withcontinue-on-error: true— failures there don't block merge but give early warning of upcoming-Ruby regressions.Services::CommandHandle: replaced&blockparameters with the Ruby 3.1+ anonymous block-forwarding form (&) — surfaced onceTargetRubyVersionwas bumped andNaming/BlockForwarding/Style/ArgumentsForwardingstarted firing.Breaking change
This raises the minimum supported Ruby — anyone on 3.0 will see
Gem::InstallErrorongem install e2b -v 0.4.0(or whatever the next release ends up being). The next release should bump to 0.4.0 rather than 0.3.6 to reflect that.Test plan
rake (Ruby 3.1)rake (Ruby 3.2)rake (Ruby 3.3)rake (Ruby 3.4)rake (Ruby 3.5)— first time this version is exercisedrake (Ruby head)— allowed to fail; informational🤖 Generated with Claude Code