Re-generate protobuf files to be compatible with google-protobuf v4.x

[valscion]

• https://github.com/protocolbuffers/protobuf/releases/tag/v26.0-rc3
• https://protobuf.dev/news/2023-04-20/

The compiled Ruby files will no longer work with google-protobuf v4.26.0 that has been released March 12, 2024.

The generated outcome is the result of

cd lib/
protoc **/*.proto --ruby_out=.

$ protoc --version
libprotoc 29.3

[valscion]

Hi @mostlyobvious or others — anything I could do here to get this over the finish line?

We are still stuck to google-protobuf v3.x unless we'd use the code from this branch.

A new major version of protobuf-nested-struct with these changes in would allow us to not use a git dependency here.

Do you want some test coverage or something here?

I've verified that bundle exec rspec still works here.

[mostlyobvious]

@valscion on it today

[valscion]

Let me know if there's anything more you need from me, happy to help ☺️

[valscion]

For what it's worth, it does seem like these changes also worked with the 3.x version of google-protobuf gem. So this change might be backwards-compatible after all.

[mostlyobvious]

Thank you for all the links and research you've done here — it was helpful. I had to remind myself the inner workings of protobuf and their versioning policy.

The last version of google-protobuf 3.x targeted protoc in version 25.7. I've regenerated the Ruby files from .proto using that particular binary version and it already gets rid of the DSL. This DSL seems to be the main breaking change going from protoc 26.x and forward.

I'll release v1.2.0 first that explicitly targets 3.25.x of google-protobuf.

Then continue bumping both: the google-protobuf and protoc versions until the latest avaiable — in separate PRs.

[mostlyobvious]

Released v1.2.0 + v1.2.1

I think at this point it should already work for your use case. I'll revisit what changes (in the gem perspective) in the newer protoc versions later.

[mostlyobvious]

Since protoc 26 and up until latest protoc 30 the generated code differs only in lack of TypeError rescue and warnings of fallbacks. So there is little need to require the newest proto version, however having at least version 26 is sensible in 2025.

I've rebased your PR , added minimal gem version requirement and will eventually release it as 2.0

[mostlyobvious]

Released v2.0.0

Let me know how it goes for you!

[valscion]

Thank you! These changes should work for us, I don't see why not. I'll let you know once we get to upgrading our protobuf-related dependencies ☺️