Require Ruby >= 3.3 and update CI Ruby versions#67
Merged
Conversation
dkisselev
approved these changes
Jun 25, 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
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
Raises the minimum supported Ruby version to 3.3 (Ruby 3.2 is now EOL) and refreshes CI accordingly.
Changes:
singed.gemspec:required_ruby_versionbumped from>= 3.2.0to>= 3.3..github/workflows/build.yml: dropped Ruby3.2from the CI test matrix; the matrix now runs3.3,3.4, and4.0..rubocop.yml:AllCops.TargetRubyVersionbumped from3.2to3.3.No
.ruby-version/.tool-versionsfiles exist, and.standard.ymlhas noTargetRubyVersion, so no changes were needed there. The README contains no explicit minimum-Ruby statement to update.Motivation
Resolves the Ruby version restrictions from rubyatscale/pack_stats#56, where supporting EOL Ruby forced older/vulnerable transitive dependencies. Dropping EOL Ruby 3.2 allows the supported set (3.3 and 3.4) to track current, non-vulnerable dependencies.
Bundler
Also bumps
BUNDLED WITHinGemfile.lockto bundler 4.0.15 (latest). The previously pinned bundler version crashes on Rubyhead(NameError: uninitialized constant Pathname::SEPARATOR_PAT) — see this failing run. Pinning the current bundler resolves it.