Skip to content

feat!: add Ruby 4.0 support, require minimum Ruby 3.4#217

Merged
josecolella merged 4 commits intomainfrom
feat/ruby-4.0-support
Mar 5, 2026
Merged

feat!: add Ruby 4.0 support, require minimum Ruby 3.4#217
josecolella merged 4 commits intomainfrom
feat/ruby-4.0-support

Conversation

@josecolella
Copy link
Collaborator

@josecolella josecolella commented Mar 5, 2026

Summary

  • Add Ruby 4.0 support: Ruby 4.0.1 (released January 2026) is now tested in CI and fully supported
  • Raise minimum Ruby to 3.4: Drop support for Ruby 3.1 (EOL March 2025), 3.2 (EOL March 2026), and 3.3 (security-only maintenance)
  • Update tooling: .ruby-version, .tool-versions, CI matrix, gemspec constraint, README version table, and Gemfile.lock all updated

Breaking Change

Minimum required Ruby version is now 3.4. Ruby 3.1, 3.2, and 3.3 are no longer supported.

Verification

  • bundle exec rspec — all 272 tests pass on Ruby 4.0.1
  • bundle exec standardrb — 49 files inspected, no offenses
  • No code changes needed for Ruby 4.0 compatibility

Test plan

  • CI passes on Ruby 4.0 matrix entry
  • CI passes on Ruby 3.4 matrix entry
  • StandardRB linter job passes

🤖 Jose's AI agent

@josecolella josecolella requested a review from a team as a code owner March 5, 2026 15:53
@gemini-code-assist
Copy link

Summary of Changes

Hello, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request significantly upgrades the project's Ruby environment by introducing support for Ruby 4.0 and enforcing a higher minimum Ruby version of 3.4. This change ensures compatibility with future Ruby releases while streamlining the development environment by removing support for older, less maintained versions. The update also involves a comprehensive refresh of gem dependencies and development configurations to maintain stability and leverage the latest features.

Highlights

  • Ruby 4.0 Support Added: The project now officially supports and is tested against Ruby 4.0.1, which is slated for release in January 2026.
  • Minimum Ruby Version Raised: The minimum required Ruby version has been increased to 3.4, discontinuing support for Ruby 3.1, 3.2, and 3.3.
  • Tooling and Dependencies Updated: Various development tooling configurations, CI matrix entries, gemspec constraints, and gem dependencies have been updated to align with the new Ruby version requirements.
Changelog
  • .ruby-version
    • Updated the specified Ruby version from 3.4.8 to 4.0.1.
  • .tool-versions
    • Updated the Ruby version for development tools from 3.4.8 to 4.0.1.
  • Gemfile.lock
    • Updated numerous gem dependencies to their latest compatible versions, including ast, debug, diff-lcs, docile, io-console, irb, json, language_server-protocol, markly, parallel, parser, psych, racc, rake, rdoc, regexp_parser, reline, rexml, rubocop, rubocop-ast, rubocop-performance, simplecov-html, standard, standard-performance, stringio, and unicode-display_width.
    • Added new direct or transitive dependencies: date, erb, pp, prettyprint, prism, tsort, and unicode-emoji.
    • Added arm64-darwin-25 to the list of supported platforms.
  • README.md
    • Removed Ruby 3.1.x, 3.2.x, and 3.3.x from the supported versions table.
    • Added Ruby 3.4.x and 4.0.x to the supported Ruby versions table.
  • openfeature-sdk.gemspec
    • Changed the minimum required Ruby version from >= 3.1 to >= 3.4.
Ignored Files
  • Ignored by pattern: .github/workflows/** (1)
    • .github/workflows/main.yml
Activity
  • The pull request author has outlined verification steps, including passing bundle exec rspec and bundle exec standardrb on Ruby 4.0.1, and confirmed no code changes were needed for Ruby 4.0 compatibility.
  • A test plan has been provided, focusing on CI pass status for Ruby 4.0 and 3.4 matrix entries, and StandardRB linter job success.
  • No human review comments or additional activity have been recorded since the pull request was created.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request successfully updates the project to support Ruby 4.0 and raises the minimum required Ruby version to 3.4. The changes across .ruby-version, .tool-versions, Gemfile.lock, README.md, and openfeature-sdk.gemspec are consistent with the stated goals. The dependency updates in Gemfile.lock are a natural consequence of the Ruby version bump, and the documentation and gemspec reflect the new minimum Ruby version correctly. The verification steps and test plan outlined in the PR description are also appropriate for these changes.

@codecov
Copy link

codecov bot commented Mar 5, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 99.65%. Comparing base (67b9796) to head (965e413).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #217   +/-   ##
=======================================
  Coverage   99.64%   99.65%           
=======================================
  Files          26       26           
  Lines         571      578    +7     
=======================================
+ Hits          569      576    +7     
  Misses          2        2           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

josecolella and others added 4 commits March 5, 2026 08:11
BREAKING CHANGE: Minimum required Ruby version is now 3.4.
Ruby 3.1, 3.2, and 3.3 are no longer supported.

- Update gemspec required_ruby_version to >= 3.4
- Update CI matrix to test Ruby 4.0 and 3.4
- Update .ruby-version and .tool-versions to 4.0.1
- Update README supported versions table
- Regenerate Gemfile.lock for Ruby 4.0 compatibility

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Signed-off-by: Jose Colella <jose.colella@gusto.com>
Align the standard linter job's ruby-version with the matrix
style convention — use "3.4" instead of pinning "3.4.8", letting
ruby/setup-ruby resolve the latest patch.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Signed-off-by: Jose Colella <jose.colella@gusto.com>
simplecov-cobertura 2.1.0 uses REXML APIs that are incompatible with
Ruby 4.0's updated REXML parser, causing "Malformed XML: No root
element" errors during coverage report generation. Version 3.x fixes
this.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Signed-off-by: Jose Colella <jose.colella@gusto.com>
Add required empty line after `include` statements flagged by
the updated Standard/RuboCop rules.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Signed-off-by: Jose Colella <jose.colella@gusto.com>
@josecolella josecolella force-pushed the feat/ruby-4.0-support branch from 02b7a39 to 965e413 Compare March 5, 2026 16:11
@josecolella josecolella merged commit f38ba40 into main Mar 5, 2026
13 checks passed
@josecolella josecolella deleted the feat/ruby-4.0-support branch March 5, 2026 16:13
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.

1 participant