deploy: 8238439

Author: copybara-service[bot]

index.xml

@@ -97,9 +97,10 @@ Compiler Plugins protoc, the Protocol Buffers Compiler, can be extended to suppo
 Numbering scheme Protobuf releases are numbered with only a minor.point number, for example 29.5.
 Each individual language runtime is versioned with that same minor.</description></item><item><title>Debugging</title><link>https://protobuf.dev/support/debugging-playbook/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://protobuf.dev/support/debugging-playbook/</guid><description>Frequently asked questions and debugging scenarios encountered by protobuf users.
 Bazel: Resolving Issues with Prebuilt Protoc As mentioned in this news article, Bazel 7 and later support builds that use a prebuilt protoc. When everything is configured correctly, this can save a lot of time building, reduce logging volume, and eliminate the need for C++ toolchain in non-C++ implementations.
-To prevent protoc compilation from source, add the following to your .</description></item><item><title>Migration Guide</title><link>https://protobuf.dev/support/migration/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://protobuf.dev/support/migration/</guid><description>Changes in v30.0 The following is a list of the breaking changes made to versions of the libraries, and how to update your code to accommodate the changes.
-This covers breaking changes announced in News Announcements for v30.x and Release Notes for v30.0.
-Replaced CMake Submodules with Fetched Deps Previously, our default CMake behavior was to use Git submodules to grab pinned dependencies. Specifying -Dprotobuf_ABSL_PROVIDER=package would flip our CMake configs to look for local installations of Abseil (with similar options for jsoncpp and gtest).</description></item><item><title>Cross-Version Runtime Guarantee</title><link>https://protobuf.dev/support/cross-version-runtime-guarantee/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://protobuf.dev/support/cross-version-runtime-guarantee/</guid><description>Protobuf language bindings have two components. The generated code (gencode) and the runtime libraries that implement common functionality for that generated code. When these come from different releases of protobuf, we are in a &amp;ldquo;cross version runtime&amp;rdquo; situation.
+To prevent protoc compilation from source, add the following to your .</description></item><item><title>Migration Guide</title><link>https://protobuf.dev/support/migration/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://protobuf.dev/support/migration/</guid><description>Changes in v34.0 The following is a list of the breaking changes made to versions of the libraries, and how to update your code to accommodate the changes.
+This covers breaking changes announced in News Announcements for v34.x and Release Notes for v34.0.
+Changes in C++ C++ bumped its major version to 7 with the 7.34.0 release. 6.33 is the final minor version release on 6.x.
+Removal of Future Macros The following macros, introduced for staged roll-out of breaking changes, were removed and their behavior is now the default:</description></item><item><title>Cross-Version Runtime Guarantee</title><link>https://protobuf.dev/support/cross-version-runtime-guarantee/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://protobuf.dev/support/cross-version-runtime-guarantee/</guid><description>Protobuf language bindings have two components. The generated code (gencode) and the runtime libraries that implement common functionality for that generated code. When these come from different releases of protobuf, we are in a &amp;ldquo;cross version runtime&amp;rdquo; situation.
 We intend to offer the following guarantees across most languages. These are the default guarantees; however, owners of protobuf code generators and runtimes may explicitly override them with more specific guarantees for that language.</description></item><item><title>Downloads</title><link>https://protobuf.dev/downloads/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://protobuf.dev/downloads/</guid><description>Release Packages Latest Version The latest release of Protocol Buffers can be found on the release page.
 Old Versions Older versions are available in our historical releases on GitHub.
 Source Code GitHub Repository Protocol Buffers source code is hosted on GitHub.</description></item><item><title>History</title><link>https://protobuf.dev/history/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://protobuf.dev/history/</guid><description>Understanding why protobuf was created and the decisions that changed it over time can help you to better use the features of the tool.

support/index.xml

@@ -2,7 +2,8 @@
 Numbering scheme Protobuf releases are numbered with only a minor.point number, for example 29.5.
 Each individual language runtime is versioned with that same minor.</description></item><item><title>Debugging</title><link>https://protobuf.dev/support/debugging-playbook/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://protobuf.dev/support/debugging-playbook/</guid><description>Frequently asked questions and debugging scenarios encountered by protobuf users.
 Bazel: Resolving Issues with Prebuilt Protoc As mentioned in this news article, Bazel 7 and later support builds that use a prebuilt protoc. When everything is configured correctly, this can save a lot of time building, reduce logging volume, and eliminate the need for C++ toolchain in non-C++ implementations.
-To prevent protoc compilation from source, add the following to your .</description></item><item><title>Migration Guide</title><link>https://protobuf.dev/support/migration/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://protobuf.dev/support/migration/</guid><description>Changes in v30.0 The following is a list of the breaking changes made to versions of the libraries, and how to update your code to accommodate the changes.
-This covers breaking changes announced in News Announcements for v30.x and Release Notes for v30.0.
-Replaced CMake Submodules with Fetched Deps Previously, our default CMake behavior was to use Git submodules to grab pinned dependencies. Specifying -Dprotobuf_ABSL_PROVIDER=package would flip our CMake configs to look for local installations of Abseil (with similar options for jsoncpp and gtest).</description></item><item><title>Cross-Version Runtime Guarantee</title><link>https://protobuf.dev/support/cross-version-runtime-guarantee/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://protobuf.dev/support/cross-version-runtime-guarantee/</guid><description>Protobuf language bindings have two components. The generated code (gencode) and the runtime libraries that implement common functionality for that generated code. When these come from different releases of protobuf, we are in a &amp;ldquo;cross version runtime&amp;rdquo; situation.
+To prevent protoc compilation from source, add the following to your .</description></item><item><title>Migration Guide</title><link>https://protobuf.dev/support/migration/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://protobuf.dev/support/migration/</guid><description>Changes in v34.0 The following is a list of the breaking changes made to versions of the libraries, and how to update your code to accommodate the changes.
+This covers breaking changes announced in News Announcements for v34.x and Release Notes for v34.0.
+Changes in C++ C++ bumped its major version to 7 with the 7.34.0 release. 6.33 is the final minor version release on 6.x.
+Removal of Future Macros The following macros, introduced for staged roll-out of breaking changes, were removed and their behavior is now the default:</description></item><item><title>Cross-Version Runtime Guarantee</title><link>https://protobuf.dev/support/cross-version-runtime-guarantee/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://protobuf.dev/support/cross-version-runtime-guarantee/</guid><description>Protobuf language bindings have two components. The generated code (gencode) and the runtime libraries that implement common functionality for that generated code. When these come from different releases of protobuf, we are in a &amp;ldquo;cross version runtime&amp;rdquo; situation.
 We intend to offer the following guarantees across most languages. These are the default guarantees; however, owners of protobuf code generators and runtimes may explicitly override them with more specific guarantees for that language.</description></item></channel></rss>