Ruby: define Google::Protobuf::VERSION in lib/google/protobuf/version.rb (#30762)
### Motivation
The `google-protobuf` gem does not expose its version in Ruby code. The version is only a string literal in `ruby/google-protobuf.gemspec`. Most gems define a `VERSION` constant in `lib/<gem>/version.rb`, and the gemspec reads it from there. This lets applications and tools read the version at runtime with `Google::Protobuf::VERSION`.
### Changes
- Add `ruby/lib/google/protobuf/version.rb`, which defines `Google::Protobuf::VERSION`.
- Make `ruby/google-protobuf.gemspec` read `s.version` from `Google::Protobuf::VERSION`.
- Require `google/protobuf/version` at the end of `ruby/lib/google/protobuf.rb`, so the constant is available after `require "google/protobuf"`.
- Add `//ruby/lib/google:protobuf/version.rb` to the `rb_bundle_fetch` sources in `WORKSPACE`, because the gemspec now requires the file.
### Required change to the internal version update tool
> [!IMPORTANT]
> The internal version update tool (the `update_versions` library that makes the "Updating version.json and repo version numbers" commits) must change after this PR merges.
The tool currently writes the Ruby version into `ruby/google-protobuf.gemspec`. The legacy `update_version.py` (removed in #9983) used this pattern:
```python
RewriteTextFile('ruby/google-protobuf.gemspec',
lambda line : re.sub(
r'^ s.version = ".*"$',
' s.version = "%s"' % GetFullVersion(rc_suffix = '.rc.'),
line))
```
After this PR, the gemspec does not contain a version literal, so that pattern matches nothing. The tool must write the version into `ruby/lib/google/protobuf/version.rb` instead, for example:
```python
RewriteTextFile('ruby/lib/google/protobuf/version.rb',
lambda line : re.sub(
r'^ VERSION = ".*"$',
' VERSION = "%s"' % GetFullVersion(rc_suffix = '.rc.'),
line))
```
If the tool does not change, the next version bump will leave `version.rb` at the old version without an error, and the gem will be published with the wrong version. `PROTOBUF_RUBY_VERSION` in `protobuf_version.bzl` still names the `.gem` file in the Bazel release rules, so the tool must continue to update both values.
Closes #30762
COPYBARA_INTEGRATE_REVIEW=https://github.com/protocolbuffers/protobuf/pull/30762 from Shopify:uk-add-version-file 36692bbd9ae1561d54622086f4c0e56ddb69fab1
PiperOrigin-RevId: 1002455477
Copyright 2008 Google LLC
Protocol Buffers (a.k.a., protobuf) are Google's language-neutral, platform-neutral, extensible mechanism for serializing structured data. You can learn more about it in protobuf's documentation.
This README file contains protobuf installation instructions. To install protobuf, you need to install the protocol compiler (used to compile .proto files) and the protobuf runtime for your chosen programming language.
Most users will find working from supported releases to be the easiest path.
If you choose to work from the head revision of the main branch your build will occasionally be broken by source-incompatible changes and insufficiently-tested (and therefore broken) behavior.
If you are using C++ or otherwise need to build protobuf from source as a part of your project, you should pin to a release commit on a release branch.
This is because even release branches can experience some instability in between release commits.
Protobuf supports Bzlmod with Bazel 8 +. Users should specify a dependency on protobuf in their MODULE.bazel file as follows.
bazel_dep(name = "protobuf", version = <VERSION>)
Users can optionally override the repo name, such as for compatibility with WORKSPACE.
bazel_dep(name = "protobuf", version = <VERSION>, repo_name = "com_google_protobuf")
Users can also add the following to their legacy WORKSPACE file.
Note that with the release of 30.x there are a few more load statements to properly set up rules_java and rules_python.
http_archive(
name = "com_google_protobuf",
strip_prefix = "protobuf-VERSION",
sha256 = ...,
url = ...,
)
load("@com_google_protobuf//:protobuf_deps.bzl", "protobuf_deps")
protobuf_deps()
load("@rules_java//java:rules_java_deps.bzl", "rules_java_dependencies")
rules_java_dependencies()
load("@rules_java//java:repositories.bzl", "rules_java_toolchains")
rules_java_toolchains()
load("@rules_python//python:repositories.bzl", "py_repositories")
py_repositories()
The protobuf compiler is written in C++. If you are using C++, please follow the C++ Installation Instructions to install protoc along with the C++ runtime.
For non-C++ users, the simplest way to install the protocol compiler is to download a pre-built binary from our GitHub release page.
In the downloads section of each release, you can find pre-built binaries in zip packages: protoc-$VERSION-$PLATFORM.zip. It contains the protoc binary as well as a set of standard .proto files distributed along with protobuf.
If you are looking for an old version that is not available in the release page, check out the Maven repository.
These pre-built binaries are only provided for released versions. If you want to use the github main version at HEAD, or you need to modify protobuf code, or you are using C++, it's recommended to build your own protoc binary from source.
If you would like to build protoc binary from source, see the C++ Installation Instructions.
Protobuf supports several different programming languages. For each programming language, you can find instructions in the corresponding source directory about how to install protobuf runtime for that specific language:
| Language | Source |
|---|---|
| C++ (include C++ runtime and protoc) | src |
| Java | java |
| Python | python |
| Objective-C | objectivec |
| C# | csharp |
| Ruby | ruby |
| Go | protocolbuffers/protobuf-go |
| PHP | php |
| Dart | dart-lang/protobuf |
| JavaScript | protocolbuffers/protobuf-javascript |
The best way to learn how to use protobuf is to follow the tutorials in our developer guide.
If you want to learn from code examples, take a look at the examples in the examples directory.
The complete documentation is available at the Protocol Buffers doc site.
Read about our version support policy to stay current on support timeframes for the language libraries.
To be alerted to upcoming changes in Protocol Buffers and connect with protobuf developers and users, join the Google Group.