No description
Find a file
Adam Cozzette 716d062d4c Create //rust:release alias for building release crates
This follows the convention we use for other languages. This CL also renames
release.sh to publish_release.sh to avoid confusion.

PiperOrigin-RevId: 733335784
2025-03-04 08:19:41 -08:00
.bazelci Add .bazelci/presubmit.yml to test protobuf on Bazel CI 2025-02-26 08:39:06 -08:00
.bcr Add .bazelci/presubmit.yml to test protobuf on Bazel CI 2025-02-26 08:39:06 -08:00
.github Temporarily disable broken aarch64 test runs. 2025-02-28 08:10:48 -08:00
bazel Internal change 2025-02-20 01:18:26 -08:00
benchmarks Upgrade abseil-cpp to 20250127 and use @com_google_absl -> @abseil-cpp and com_google_googletest -> @googletest canonical BCR names. 2025-02-10 09:43:53 -08:00
build_defs Fix redundant clang-cl and msvc platform constraint for Bazel 8 compatibility and enable Bazel 8 presubmits in BCR. 2025-02-14 14:48:49 -08:00
ci Upgrade zlib to BCR patch 5 and remove -Wunknown-warning-option for macOS. 2025-02-03 12:21:54 -08:00
cmake Auto-generate files after cl/730923037 2025-02-25 17:59:36 +00:00
compatibility Run buildifier 2025-02-19 09:27:02 -08:00
conformance Bazel 8 compatibility clean-ups 2025-02-28 10:54:27 -08:00
csharp Improve performace of repeated packed fixedSize fields (#19667) 2025-02-20 22:14:52 -08:00
docs Reserve new extensions for protokt v1 (#20485) 2025-02-27 11:25:17 -08:00
editions IWYU cleanup in C++ runtime code 2025-03-03 22:47:08 -08:00
editors protobuf-mode: add edition keyword for syntax highlighting 2024-08-23 07:17:25 -07:00
examples Run buildifier 2025-02-19 09:27:02 -08:00
go protobuf: add //:go_features_proto Bazel alias 2025-02-20 00:45:10 -08:00
hpb hpb: refactor SetExtension to have a sole entry point 2025-02-13 08:14:49 -08:00
hpb_generator hbp: remove genn'd forwarding header 2025-02-12 07:41:34 -08:00
java Automated rollback of commit 6d2f6fcf66. 2025-02-26 11:10:15 -08:00
lua Run buildifier 2025-02-19 09:27:02 -08:00
objectivec Internal Change 2025-02-21 10:50:35 -08:00
php Auto-generate files after cl/732305859 2025-03-01 01:24:24 +00:00
pkg Remove protoc-gen-upb_minitable from CMake build and protobuf_codegen crate 2025-02-20 14:07:21 -08:00
python Add more detail to the comment for GetMessageClassesForFiles 2025-03-03 18:41:35 -08:00
ruby Auto-generate files after cl/732305859 2025-03-01 01:24:24 +00:00
rust Create //rust:release alias for building release crates 2025-03-04 08:19:41 -08:00
src Add Clang nullability annotations to reflection.h APIs (RepeatedFieldRef, etc) 2025-03-04 05:59:22 -08:00
third_party Internal change 2025-02-24 11:25:25 -08:00
toolchain Remove test platform specification from release config 2025-02-25 20:52:59 -08:00
upb Merge consecutive unknown fields when parsing with aliasing on. This shows large improvements in benchmarks on arm64 little cores. 2025-02-28 17:15:31 -08:00
upb_generator upb: delete functions in map_gencode_util. They're unused after the Map iterator API change. 2025-02-27 15:23:13 -08:00
.bazelignore Internal changes 2024-10-17 11:33:01 -07:00
.bazeliskrc Add .bazeliskrc for protobuf repo to tell bazelisk to use 7.1.2 by default. 2025-01-06 14:41:40 -08:00
.bazelrc Delete repo_env=BAZEL_NO_APPLE_CPP_TOOLCHAIN=1 flag from .bazelrc since it is not needed and causing errors. 2025-02-21 11:08:17 -08:00
.clang-format Clean up a few stray files that ended up in the wrong place 2023-09-27 09:30:44 -07:00
.gitignore Add a multi-platform Gemfile.lock (#19804) 2025-01-10 19:39:38 -08:00
.gitmodules Internal changes 2024-10-17 11:33:01 -07:00
.readthedocs.yml Automated rollback of commit 4dc164884c. 2024-06-10 16:32:18 -07:00
appveyor.bat [dotnet, csharp] Run tests for supported platforms .NET 6, .NET Framework 4.6.2 (#12378) 2023-04-10 13:28:23 -07:00
appveyor.yml Upgrade to MSVC 2017 (#10437) 2022-08-22 14:29:12 -07:00
BUILD.bazel protobuf: add //:go_features_proto Bazel alias 2025-02-20 00:45:10 -08:00
Cargo.bazel.lock Upgrade to rules_rust v0.54.1 2024-12-03 08:37:46 -08:00
Cargo.lock Rename #[googletest::test] to #[gtest] 2024-08-12 01:48:49 -07:00
CMakeLists.txt Updating version.json and repo version numbers to: 31.0-dev (#20237) 2025-02-06 09:41:40 -08:00
CODE_OF_CONDUCT.md Add a code of conduct based on https://www.contributor-covenant.org/ and https://github.com/carbon-language/carbon-lang/blob/trunk/CODE_OF_CONDUCT.md 2022-12-01 09:29:45 -08:00
CONTRIBUTING.md Replace master with main in URLs & docs 2022-04-12 10:25:08 -07:00
CONTRIBUTORS.txt Match service argument names to abstract interface (#9418) 2022-02-03 09:14:44 -08:00
fix_permissions.sh Set execute bit on files if and only if they begin with (#!). (#7347) 2020-04-01 15:28:25 -07:00
generate_descriptor_proto.sh Release prototype of Protobuf Editions. 2023-06-30 20:18:49 -07:00
global.json Update .NET SDKs to LTS versions 2021-11-10 08:49:53 +13:00
google3_export_generated_files.sh Bump protobuf to latest upb version. 2023-01-14 00:11:12 -08:00
LICENSE Cleanup LICENSE file. 2018-03-26 15:03:41 -07:00
maven_install.json Make Java consistently reject unmatched end-group tag. 2024-12-11 13:47:29 -08:00
MODULE.bazel Add notices.h with information about our dependencies' licenses and add --notices flag to protoc to print the contents of that file. 2025-02-25 09:50:30 -08:00
PrivacyInfo.xcprivacy Add PrivacyInfo.xcprivacy (#15557) 2024-01-25 00:31:38 -08:00
protobuf.bzl Run buildifier 2025-02-19 09:27:02 -08:00
Protobuf.podspec Updating version.json and repo version numbers to: 31.0-dev (#20237) 2025-02-06 09:41:40 -08:00
protobuf_deps.bzl Upgrade abseil-cpp to 20250127 and use @com_google_absl -> @abseil-cpp and com_google_googletest -> @googletest canonical BCR names. 2025-02-10 09:43:53 -08:00
protobuf_release.bzl Internal change 2024-03-27 05:50:55 -07:00
protobuf_version.bzl Updating version.json and repo version numbers to: 31.0-dev (#20237) 2025-02-06 09:41:40 -08:00
README.md Test against bazel 8.0.0, update dependencies to bazel 8 compatible versions, and remove protobuf_extra_deps. 2025-01-27 11:39:04 -08:00
regenerate_stale_files.sh Remove upb gencode from upb/cmake/ 2025-02-19 12:38:58 -08:00
SECURITY.md grammar nit 2021-08-13 14:50:07 -04:00
version.json Updating version.json and repo version numbers to: 31.0-dev (#20237) 2025-02-06 09:41:40 -08:00
WORKSPACE Fix redundant clang-cl and msvc platform constraint for Bazel 8 compatibility and enable Bazel 8 presubmits in BCR. 2025-02-14 14:48:49 -08:00
WORKSPACE.bzlmod Remove --noenable_bzlmod from .bazelrc 2025-01-31 16:45:18 -08:00

Protocol Buffers - Google's data interchange format

OpenSSF Scorecard

Copyright 2023 Google LLC

Overview

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.

Working With Protobuf Source Code

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.

Bazel with Bzlmod

Protobuf supports Bzlmod with Bazel 7 +. 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")

Bazel with WORKSPACE

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()

Protobuf Compiler Installation

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 Runtime Installation

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

Quick Start

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.

Documentation

The complete documentation is available at the Protocol Buffers doc site.

Support Policy

Read about our version support policy to stay current on support timeframes for the language libraries.

Developer Community

To be alerted to upcoming changes in Protocol Buffers and connect with protobuf developers and users, join the Google Group.