deploy: 8c16090

copybara-service[bot] · copybara-service[bot] · commit 7cd32e266062 · 2026-01-28T17:21:54.000Z
diff --git a/index.xml b/index.xml
@@ -308,7 +308,7 @@ Motivation Currently Protobuf debug APIs print every field in a proto into human
 The following sections outline the set of breaking changes that we plan to include in the 26.0 release of protocol buffers. Note that plans can and do change. These are potential breaking changes to be aware of, but they may not happen in this particular release, or they may not happen at all.</description></item><item><title>Changes Announced on February 27, 2024</title><link>https://protobuf.dev/news/2024-02-27/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://protobuf.dev/news/2024-02-27/</guid><description>Dropping Ruby 2.7 Support As per our official Ruby support policy, we will be dropping support for Ruby 2.7 and lower on March 31, 2024. The minimum supported Ruby version will be 3.0.</description></item><item><title>Changes announced February 5, 2024</title><link>https://protobuf.dev/news/2024-02-05/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://protobuf.dev/news/2024-02-05/</guid><description>This topic covers breaking changes in Java, C++, and Python in the 26.x line.
 JSON Formatter Option Changes Starting in the 26.x line, the JSON formatter option to print default-valued fields is replaced with a fixed way to handle proto2 and proto3 optional fields consistently.
 Java: includingDefaultValueFields() is replaced with alwaysPrintFieldsWithNoPresence(). C++: always_print_default_values is replaced with always_print_fields_with_no_presence=True. Py: including_default_value_fields=True is replaced with always_print_fields_with_no_presence=True. The new flag behaves identically to the old flag on proto3 messages, but no longer applies to proto2 optional fields.</description></item><item><title>Changes Announced on January 16, 2026</title><link>https://protobuf.dev/news/2026-01-16/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://protobuf.dev/news/2026-01-16/</guid><description>Prebuilt proto compiler (protoc) for Bazel In an effort to speed up builds, protobuf 33.4 offers an option to skip re-compiling Protobuf tools and runtimes and use a pre-built protoc binary, available to Bazel 7 and later. Using a pre-built protoc also avoids build failures from incompatible or non-hermetic C++ compilation toolchain installed on your machine.
-To use the prebuilt protoc, upgrade to protobuf version 33.4 or later, and set the --incompatible_enable_proto_toolchain_resolution and --@protobuf//bazel/toolchains:prefer_prebuilt_protoc flags.</description></item><item><title>Changes announced January 23, 2025</title><link>https://protobuf.dev/news/2025-01-23/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://protobuf.dev/news/2025-01-23/</guid><description>Poison Java gencode We are patching a change into the 25.x branch that will poison Java gencode that was created prior to the 3.21.7 release. We will then mark all versions of Java protobuf from 3.21.7 through 3.25.5 as vulnerable to the footmitten CVE.
+To use the prebuilt protoc, upgrade to protobuf version 33.4 or later, and set the --incompatible_enable_proto_toolchain_resolution and --@protobuf//bazel/flags:prefer_prebuilt_protoc flags.</description></item><item><title>Changes announced January 23, 2025</title><link>https://protobuf.dev/news/2025-01-23/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://protobuf.dev/news/2025-01-23/</guid><description>Poison Java gencode We are patching a change into the 25.x branch that will poison Java gencode that was created prior to the 3.21.7 release. We will then mark all versions of Java protobuf from 3.21.7 through 3.25.5 as vulnerable to the footmitten CVE.
 After this change is patched in, protobuf will throw an UnsupportedOperationException from the makeExtensionsImmutable method unless you set the system property &amp;ldquo;-Dcom.google.protobuf.use_unsafe_pre22_gencode&amp;rdquo;. Using this system property can buy you some time if you can&amp;rsquo;t update your code immediately, but should be considered a short-term workaround.</description></item><item><title>Changes announced January 31, 2024</title><link>https://protobuf.dev/news/2024-01-31/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://protobuf.dev/news/2024-01-31/</guid><description>This topic covers breaking changes in Python in the 26.x line.
 Python Breaking Changes Removing setup.py and setup.cfg support from GitHub In the 26.x release, setup.py and setup.cfg will no longer be present in the python/ directory of the GitHub repository or GitHub release tarballs. This means it will no longer be possible to build a Python package directly from the GitHub repo or release tarball.
 The Python source packages published on PyPI will continue to have a setup.</description></item><item><title>Changes announced January 5, 2024</title><link>https://protobuf.dev/news/2024-01-05/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://protobuf.dev/news/2024-01-05/</guid><description>This topic covers breaking changes in Ruby and Python in the 26.x line.
diff --git a/news/2026-01-16/index.html b/news/2026-01-16/index.html
@@ -9,9 +9,9 @@
 failures from incompatible or non-hermetic C++ compilation toolchain installed
 on your machine.</p><p>To use the prebuilt protoc, upgrade to protobuf version 33.4 or later, and set
 the <code>--incompatible_enable_proto_toolchain_resolution</code> and
-<code>--@protobuf//bazel/toolchains:prefer_prebuilt_protoc</code> flags. The first flag is
-set by default in Bazel 9 onwards.</p><p>In the breaking v34 release, protobuf will change the default of
-<code>--@protobuf//bazel/toolchains:prefer_prebuilt_protoc</code> to true.</p><h3 id=reasons-not-to-use-the-prebuilt-compiler>Reasons not to use the prebuilt compiler</h3><p>There are some use cases in which using the prebuilt protoc is not recommended:</p><ul><li>Your corporate security policy requires all dependencies be built from
+<code>--@protobuf//bazel/flags:prefer_prebuilt_protoc</code> flags. The first flag is set
+by default in Bazel 9 onwards.</p><p>In the breaking v34 release, protobuf will change the default of
+<code>--@protobuf//bazel/flags:prefer_prebuilt_protoc</code> to true.</p><h3 id=reasons-not-to-use-the-prebuilt-compiler>Reasons not to use the prebuilt compiler</h3><p>There are some use cases in which using the prebuilt protoc is not recommended:</p><ul><li>Your corporate security policy requires all dependencies be built from
 source.</li><li>You need to build for the exec platform with a specific compiler or specific
 compiler flags.</li><li>You are making changes to protoc, itself, and want to ensure that those
 changes are tested.</li></ul><h3 id=troubleshooting>Troubleshooting</h3><p>For information on troubleshooting the prebuilt protoc compiler configuration,
diff --git a/news/index.xml b/news/index.xml
@@ -15,7 +15,7 @@ Motivation Currently Protobuf debug APIs print every field in a proto into human
 The following sections outline the set of breaking changes that we plan to include in the 26.0 release of protocol buffers. Note that plans can and do change. These are potential breaking changes to be aware of, but they may not happen in this particular release, or they may not happen at all.</description></item><item><title>Changes Announced on February 27, 2024</title><link>https://protobuf.dev/news/2024-02-27/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://protobuf.dev/news/2024-02-27/</guid><description>Dropping Ruby 2.7 Support As per our official Ruby support policy, we will be dropping support for Ruby 2.7 and lower on March 31, 2024. The minimum supported Ruby version will be 3.0.</description></item><item><title>Changes announced February 5, 2024</title><link>https://protobuf.dev/news/2024-02-05/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://protobuf.dev/news/2024-02-05/</guid><description>This topic covers breaking changes in Java, C++, and Python in the 26.x line.
 JSON Formatter Option Changes Starting in the 26.x line, the JSON formatter option to print default-valued fields is replaced with a fixed way to handle proto2 and proto3 optional fields consistently.
 Java: includingDefaultValueFields() is replaced with alwaysPrintFieldsWithNoPresence(). C++: always_print_default_values is replaced with always_print_fields_with_no_presence=True. Py: including_default_value_fields=True is replaced with always_print_fields_with_no_presence=True. The new flag behaves identically to the old flag on proto3 messages, but no longer applies to proto2 optional fields.</description></item><item><title>Changes Announced on January 16, 2026</title><link>https://protobuf.dev/news/2026-01-16/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://protobuf.dev/news/2026-01-16/</guid><description>Prebuilt proto compiler (protoc) for Bazel In an effort to speed up builds, protobuf 33.4 offers an option to skip re-compiling Protobuf tools and runtimes and use a pre-built protoc binary, available to Bazel 7 and later. Using a pre-built protoc also avoids build failures from incompatible or non-hermetic C++ compilation toolchain installed on your machine.
-To use the prebuilt protoc, upgrade to protobuf version 33.4 or later, and set the --incompatible_enable_proto_toolchain_resolution and --@protobuf//bazel/toolchains:prefer_prebuilt_protoc flags.</description></item><item><title>Changes announced January 23, 2025</title><link>https://protobuf.dev/news/2025-01-23/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://protobuf.dev/news/2025-01-23/</guid><description>Poison Java gencode We are patching a change into the 25.x branch that will poison Java gencode that was created prior to the 3.21.7 release. We will then mark all versions of Java protobuf from 3.21.7 through 3.25.5 as vulnerable to the footmitten CVE.
+To use the prebuilt protoc, upgrade to protobuf version 33.4 or later, and set the --incompatible_enable_proto_toolchain_resolution and --@protobuf//bazel/flags:prefer_prebuilt_protoc flags.</description></item><item><title>Changes announced January 23, 2025</title><link>https://protobuf.dev/news/2025-01-23/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://protobuf.dev/news/2025-01-23/</guid><description>Poison Java gencode We are patching a change into the 25.x branch that will poison Java gencode that was created prior to the 3.21.7 release. We will then mark all versions of Java protobuf from 3.21.7 through 3.25.5 as vulnerable to the footmitten CVE.
 After this change is patched in, protobuf will throw an UnsupportedOperationException from the makeExtensionsImmutable method unless you set the system property &amp;ldquo;-Dcom.google.protobuf.use_unsafe_pre22_gencode&amp;rdquo;. Using this system property can buy you some time if you can&amp;rsquo;t update your code immediately, but should be considered a short-term workaround.</description></item><item><title>Changes announced January 31, 2024</title><link>https://protobuf.dev/news/2024-01-31/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://protobuf.dev/news/2024-01-31/</guid><description>This topic covers breaking changes in Python in the 26.x line.
 Python Breaking Changes Removing setup.py and setup.cfg support from GitHub In the 26.x release, setup.py and setup.cfg will no longer be present in the python/ directory of the GitHub repository or GitHub release tarballs. This means it will no longer be possible to build a Python package directly from the GitHub repo or release tarball.
 The Python source packages published on PyPI will continue to have a setup.</description></item><item><title>Changes announced January 5, 2024</title><link>https://protobuf.dev/news/2024-01-05/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://protobuf.dev/news/2024-01-05/</guid><description>This topic covers breaking changes in Ruby and Python in the 26.x line.
