Ruby 4.0 support - just needs a new gem release

[seuros]

Hey,

Ruby 4.0.0 was released on Christmas and the current google-protobuf gem (4.33.2) has required_ruby_version set to < 3.5.dev, >= 3.1.

This constraint is baked in at build time for the prebuilt platform gems. The actual code works fine on Ruby 4.0 - the next release pipeline will automatically pick up the correct Ruby version, no code changes needed.

Just waiting on the next release to unblock Ruby 4.0 users.

Thanks!

[khasinski]

Any chance for a quick release? 👀 The change looks minor and this would really help

[JasonLunn]

I am currently working on the internal test infrastructure changes needed to support Ruby 4.0. Without it, no tests will actually run under the new version.

[seuros]

Thank you .

Could you add support to ruby-head while you are on it ?

This will allow us (gems maintainers) to test future versions and to not have this gem as a choke point)

[JasonLunn]

Asking to understand: how would a ruby-head test configuration for protobuf be helpful to other gem maintainers? I'm not actually clear how useful it would be to the Protobuf team, given it is inherently non-hermetic, so I'm having a hard time seeing how it helps anyone that has a protobuf dependency... If it breaks, how will we know it's a problem with protobuf vs unreleased changes in ruby?

[seuros]

The issue is that we cannot run ruby-head if the dependent gems are not tested without being in the dark.

If i see that this gem has a red test suite in ruby 4.1.dev, i'm not going to spend time trying to debug on my side.