Skip to content

Require Ruby >= 3.3 and update CI Ruby versions#29

Merged
dduugg merged 2 commits into
mainfrom
bump-min-ruby-3.3
Jun 25, 2026
Merged

Require Ruby >= 3.3 and update CI Ruby versions#29
dduugg merged 2 commits into
mainfrom
bump-min-ruby-3.3

Conversation

@dduugg

@dduugg dduugg commented Jun 25, 2026

Copy link
Copy Markdown
Contributor

Summary

Ruby 3.2 is now EOL. This PR raises the minimum supported Ruby to 3.3 (the lowest supported version). The supported set is 3.3 and 3.4 (latest stable 3.4.9; 3.5 is preview-only and not included).

Motivation: resolve Ruby version restrictions from rubyatscale/pack_stats#56, where supporting EOL Ruby forced older/vulnerable transitive dependencies.

Changes

  • code_teams.gemspec: required_ruby_version raised from >= 3.2 to >= 3.3.
  • .rubocop.yml: TargetRubyVersion raised from 3.2 to 3.3.

Notes

  • CI workflows (.github/workflows/*.yml) delegate to rubyatscale/shared-config reusable workflows and contain no inline Ruby version matrices, so no workflow edits were needed.
  • No .ruby-version / .tool-versions files exist in this repo.
  • No bundle install was run and Gemfile.lock is unchanged.

Bundler

Also bumps BUNDLED WITH in Gemfile.lock to bundler 4.0.15 (latest). The previously pinned bundler version crashes on Ruby head (NameError: uninitialized constant Pathname::SEPARATOR_PAT) — see this failing run. Pinning the current bundler resolves it.

@dduugg dduugg requested a review from a team as a code owner June 25, 2026 21:13
@github-project-automation github-project-automation Bot moved this to Triage in Modularity Jun 25, 2026
@dduugg dduugg merged commit ea53808 into main Jun 25, 2026
6 checks passed
@dduugg dduugg deleted the bump-min-ruby-3.3 branch June 25, 2026 21:37
@github-project-automation github-project-automation Bot moved this from Triage to Done in Modularity Jun 25, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

2 participants