[Ruby] Drop support for EOL Ruby 3.1 and clean up by larouxn · Pull Request #41435 · grpc/grpc

larouxn · 2026-01-17T03:49:15Z

Proposing we drop support for Ruby 3.1 once it reaches 1 year EOL this coming March 26 2026.

References

linux-foundation-easycla · 2026-01-17T03:49:23Z

The committers listed above are authorized under a signed CLA.

✅ login: asheshvidyut / name: Ashesh Vidyut (d9bce8f, 23ce180, 2a916ab, 49fd045, 4d54f31, 5604426, 566a96e, 627da3f, 77785f1, 97ff0b4, a236b62, c244a02, ca94263, e1c9964, e995ad3)
✅ login: larouxn / name: Nicholas La Roux (25f4ec4, 3c55797, 75d8f16)

gemini-code-assist · 2026-01-17T03:49:30Z

Summary of Changes

Hello @larouxn, I'm Gemini Code Assist¹! 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 updates the project's minimum supported Ruby version to 3.2, aligning with the end-of-life status of Ruby 3.1. This change ensures that the project maintains compatibility with actively supported Ruby versions and encourages users to upgrade to more recent, secure, and performant environments.

Highlights

Ruby Version Support: The minimum required Ruby version has been updated from 3.1 to 3.2 in the project's gemspec files.
Documentation Update: Project documentation, specifically the README.md, has been revised to reflect the new minimum Ruby version requirement of 3.2+ for both prerequisites and build instructions.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

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.

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

gemini-code-assist

Code Review

This pull request correctly updates the project to drop support for Ruby 3.1 by setting the minimum required Ruby version to 3.2. The changes are consistently applied across the gemspec, gemspec.template, and the README.md documentation. The modifications in the README also correctly update the installation instructions. The changes are accurate and align with the pull request's goal of maintaining support for active Ruby versions. As a follow-up, you might consider simplifying the have_ruby_abi_version method in src/ruby/ext/grpc/extconf.rb, as some of its logic becomes redundant with the new minimum Ruby version of 3.2.

chadlwilson · 2026-01-24T04:42:32Z

The Google policy/practice is to only drop 1 year after EOL I believe. See #39607 (comment) and #38515 (comment) (which is why I didn't drop it immediately with the ruby 4.0 cross compile support in #41324 )

https://github.com/google/oss-policies-info/blob/main/foundational-ruby-support-matrix.md

https://docs.cloud.google.com/ruby/getting-started/supported-ruby-versions

Next update is scheduled for 12 months from 3.1 EOL (March 26 2026)

chadlwilson · 2026-01-24T04:45:30Z

This is also missing some needed cleanup to the cross compile versions (RUBY_CC_VERSIONS) and the test images, distrib test matrix and Bazel lock files.

larouxn · 2026-01-24T16:00:27Z

👋 Hey @chadlwilson, thanks for the info! I hadn't yet seen foundational-ruby-support-matrix.md nor that supported-ruby-versions page. Good call out. We indeed should not merge this or anything like it until March 26. 👍

As for the missing cleanup, I have gone ahead and cleaned up everything relevant I could find. If something seems off please let me know or if you plan to tackle this in March and would rather we close this PR that's fine too.

chadlwilson · 2026-01-24T16:49:51Z

Ahh, no worries, will leave that decision on leaving the PR open to you/maintainers, but I suppose you could mark as draft for now to signal its pending state. Sadly there seem to be a lot of ancient/stale/irrelevant PRs open here as it is. 😔

It’ll need rebasing after 4.0 precompile support is merged (hopefully soon) and will likely attract conflicts over time and need some later rebases.

I’m just an external contributor as well - so just sharing what I had learned from earlier interactions with the team re: Google’s policies. 👍

larouxn · 2026-01-24T17:02:49Z

It’ll need rebasing after 4.0 precompile support is merged (hopefully soon) and will likely attract conflicts over time and need some later rebases.

I did notice that's not in yet. For sure will need some rebase + merge conflict resolution after that and come March.

Appreciate the infos. Let's go with marking this PR as a draft for now.

chadlwilson · 2026-02-04T08:58:52Z

The 4.0 update has been merged now, so you can probably rebase this in prep if you'd like 👍

larouxn · 2026-02-04T16:15:28Z

The 4.0 update has been merged now, so you can probably rebase this in prep if you'd like 👍

Thanks for the heads up. Have rebased on master. Should be good come March 26th. 🙌

larouxn · 2026-02-04T18:20:22Z

Now that Ruby 4 support is in, marking as ready for review so we can hopefully get some eyes prior to March 26th. 🙏

chadlwilson · 2026-02-04T19:46:02Z

Most of the possible issues will be with the tests on generic images which are done with the min Ruby version, which you've correctly bumped (I think).

So it'll need test images to be rebuilt and pushed by a Googler and a change merged to expected hashes - which would then need to be redone as soon as any other changes to Dockerfiles are merged to master in the interim 2 months. So I suspect there might not be much enthusiasm for doing it so far out.

But can try your luck! :)

sergiitk · 2026-02-19T17:31:37Z

@larouxn - just an FYI, normally you'd want to ping/assign @asheshvidyut and @zarinn3pal: I'm the Python TL, just happened to help sometimes with Ruby when those two are out.

I don't mind helping, but I'm not always able to get to these tickets in a timely manner.

larouxn · 2026-02-19T17:50:32Z

👋 Hey @sergiitk, super appreciate you tagging in the correct people. Thanks! 🙏

One quick note though, GitHub says I requested your review but that was actually done automatically via codeowners. I don't have the ability/permission to do anything with reviewers in this repo. 😅

grpc/.github/CODEOWNERS

Line 10 in ce8dc97

/tools/dockerfile/** @sergiitk

asheshvidyut · 2026-04-28T04:21:22Z

I will take this forward from here.

Thanks @larouxn and @chadlwilson for your contributions.

chadlwilson · 2026-04-28T05:22:06Z

Thanks for your work @asheshvidyut 🙏🏻

chadlwilson · 2026-04-28T10:01:13Z

 RUN /bin/bash -l -c "echo 'gem: --no-document' > ~/.gemrc"
 RUN /bin/bash -l -c "echo 'export PATH=/usr/local/rvm/bin:$PATH' >> ~/.bashrc"
-RUN /bin/bash -l -c "echo 'rvm --default use ruby-3.2.11' >> ~/.bashrc"
+RUN /bin/bash -l -c "echo 'rvm --default use ruby-3.2.0' >> ~/.bashrc"


I wonder what the rationale is behind running tests using old, insecure, buggy ruby versions instead of latest patch release?

Thanks for pointing it out. I will revert it. I got introduced by merge conf resolution.

Ahh ok, I wondered if you were hitting some kind of bug 👍🏻

Proposing we drop support for Ruby 3.1 once it reaches 1 year EOL this coming March 26 2026. References - https://github.com/google/oss-policies-info/blob/main/foundational-ruby-support-matrix.md - https://docs.cloud.google.com/ruby/getting-started/supported-ruby-versions - https://www.ruby-lang.org/en/downloads/branches/ - https://endoflife.date/ruby Closes grpc#41435 COPYBARA_INTEGRATE_REVIEW=grpc#41435 from larouxn:drop_support_for_eol_ruby_3.1 e995ad3 PiperOrigin-RevId: 909865176

github-actions Bot added the lang/ruby label Jan 17, 2026

gemini-code-assist Bot reviewed Jan 17, 2026

View reviewed changes

larouxn force-pushed the drop_support_for_eol_ruby_3.1 branch from f609825 to 8c7a69f Compare January 17, 2026 04:03

larouxn changed the title ~~Drop support for EOL Ruby 3.1~~ Drop support for EOL Ruby 3.1 and clean up Jan 17, 2026

larouxn force-pushed the drop_support_for_eol_ruby_3.1 branch from 8c7a69f to 2e5a9a5 Compare January 24, 2026 15:59

larouxn requested a review from sergiitk as a code owner January 24, 2026 15:59

larouxn changed the title ~~Drop support for EOL Ruby 3.1 and clean up~~ [Paused until March 26] Drop support for EOL Ruby 3.1 and clean up Jan 24, 2026

larouxn marked this pull request as draft January 24, 2026 17:03

chadlwilson approved these changes Jan 26, 2026

View reviewed changes

larouxn force-pushed the drop_support_for_eol_ruby_3.1 branch from 2e5a9a5 to 906946e Compare February 4, 2026 16:14

larouxn changed the title ~~[Paused until March 26] Drop support for EOL Ruby 3.1 and clean up~~ Drop support for EOL Ruby 3.1 and clean up Feb 4, 2026

larouxn marked this pull request as ready for review February 4, 2026 18:20

larouxn force-pushed the drop_support_for_eol_ruby_3.1 branch from 906946e to 8b0d806 Compare February 14, 2026 17:02

sergiitk requested review from asheshvidyut and zarinn3pal and removed request for sergiitk February 19, 2026 17:29

sergiitk assigned asheshvidyut Feb 19, 2026

run tools/dockerfile/push_testing_images.sh

a236b62

asheshvidyut added the kokoro:run label Apr 28, 2026

resolve merge conf

5604426

grpc-kokoro removed the kokoro:run label Apr 28, 2026

asheshvidyut added the kokoro:run label Apr 28, 2026

grpc-kokoro removed the kokoro:run label Apr 28, 2026

fix images by running push_testing_images.sh

2a916ab

asheshvidyut added the kokoro:run label Apr 28, 2026

grpc-kokoro removed the kokoro:run label Apr 28, 2026

fix sanity

77785f1

chadlwilson reviewed Apr 28, 2026

View reviewed changes

asheshvidyut added 2 commits April 28, 2026 15:51

update version 3.2.0 -> 3.2.11

97ff0b4

run push_testing_images.sh

23ce180

asheshvidyut added the kokoro:run label Apr 28, 2026

grpc-kokoro removed the kokoro:run label Apr 28, 2026

asheshvidyut added 2 commits April 28, 2026 10:49

fix ruby

627da3f

fix image

c244a02

asheshvidyut added the kokoro:run label Apr 28, 2026

grpc-kokoro removed the kokoro:run label Apr 28, 2026

merge master and run tools/dockerfile/push_testing_images.sh

e995ad3

asheshvidyut added the kokoro:run label May 4, 2026

grpc-kokoro removed the kokoro:run label May 4, 2026

grpc-checks Bot added bloat/improvement and removed bloat/none labels May 4, 2026

copybara-service Bot closed this in 61b93b0 May 4, 2026

larouxn deleted the drop_support_for_eol_ruby_3.1 branch May 4, 2026 10:48

Conversation

larouxn commented Jan 17, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

linux-foundation-easycla Bot commented Jan 17, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

gemini-code-assist Bot commented Jan 17, 2026

Summary of Changes

Highlights

Footnotes

Uh oh!

gemini-code-assist Bot left a comment

Choose a reason for hiding this comment

Code Review

Uh oh!

chadlwilson commented Jan 24, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

chadlwilson commented Jan 24, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

larouxn commented Jan 24, 2026

Uh oh!

chadlwilson commented Jan 24, 2026

Uh oh!

larouxn commented Jan 24, 2026

Uh oh!

chadlwilson commented Feb 4, 2026

Uh oh!

larouxn commented Feb 4, 2026

Uh oh!

larouxn commented Feb 4, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

chadlwilson commented Feb 4, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

sergiitk commented Feb 19, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

larouxn commented Feb 19, 2026

Uh oh!

asheshvidyut commented Apr 28, 2026

Uh oh!

chadlwilson commented Apr 28, 2026

Uh oh!

chadlwilson Apr 28, 2026

Choose a reason for hiding this comment

Uh oh!

asheshvidyut Apr 28, 2026

Choose a reason for hiding this comment

Uh oh!

chadlwilson Apr 28, 2026

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

6 participants

larouxn commented Jan 17, 2026 •

edited

Loading

linux-foundation-easycla Bot commented Jan 17, 2026 •

edited

Loading

chadlwilson commented Jan 24, 2026 •

edited

Loading

chadlwilson commented Jan 24, 2026 •

edited

Loading

larouxn commented Feb 4, 2026 •

edited

Loading

chadlwilson commented Feb 4, 2026 •

edited

Loading

sergiitk commented Feb 19, 2026 •

edited

Loading