You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: index.xml
+3-2Lines changed: 3 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -322,7 +322,8 @@ Dropping Ruby 2.6 Support As per our official Ruby support policy, we will be dr
322
322
After this point, you can continue to use Bazel, or another build system, to build Protobuf. You can read more about building from source in the Protobuf Java README.</description></item><item><title>Changes Announced on June 27, 2025</title><link>https://protobuf.dev/news/2025-06-27/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://protobuf.dev/news/2025-06-27/</guid><description>Edition 2024 We are planning to release Protobuf Edition 2024 in 32.x in Q3 2025.
323
323
These describe changes as we anticipate them being implemented, but due to the flexible nature of software some of these changes may not land or may vary from how they are described in this topic.
324
324
More documentation on Edition 2024 will be published in Feature Settings for Editions, including information on migrating from Edition 2023.</description></item><item><title>Changes Announced on June 29, 2023</title><link>https://protobuf.dev/news/2023-06-29/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://protobuf.dev/news/2023-06-29/</guid><description>TL;DR: We are planning to release Protobuf Editions to the open source project in the second half of 2023. While there is no requirement to move from proto2/proto3 syntax to Editions syntax at initial release, we encourage you to plan a move in your software project&rsquo;s future timeline.
325
-
Protobuf Editions Protobuf Editions replace the proto2 and proto3 designations that we have used for Protocol Buffers. Instead of adding syntax = &quot;proto2&quot; or syntax = &quot;proto3&quot; at the top of proto definition files, you use an edition number, such as edition = &quot;2024&quot;, to specify the default behaviors your file will have.</description></item><item><title>Changes Announced on March 18, 2025</title><link>https://protobuf.dev/news/2025-03-18/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://protobuf.dev/news/2025-03-18/</guid><description>Dropping Ruby 3.0 Support As per our official Ruby support policy, we will be dropping support for Ruby 3.0 and lower in Protobuf version 31, due to release in April, 2025. The minimum supported Ruby version will be 3.1.</description></item><item><title>Changes announced May 6, 2022</title><link>https://protobuf.dev/news/2022-05-06/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://protobuf.dev/news/2022-05-06/</guid><description>Versioning We changed our versioning scheme to enable more-nimble updates to language-specific parts of Protocol Buffers. In the new scheme, each language has its own major version that can be incremented independently of other languages, as covered later in this topic with the Python release. The minor and patch versions, however, will remain coupled. This allows us to introduce breaking changes into some languages without requiring a bump of the major version in languages that do not experience a breaking change.</description></item><item><title>Changes Announced on November 7, 2024</title><link>https://protobuf.dev/news/2024-11-07/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://protobuf.dev/news/2024-11-07/</guid><description>The following sections cover planned breaking changes in the v30 release, expected in 2025 Q1. Also included are some changes that aren&rsquo;t breaking but may require action on your part. These are in addition to those mentioned in the News article from October 2.
325
+
Protobuf Editions Protobuf Editions replace the proto2 and proto3 designations that we have used for Protocol Buffers. Instead of adding syntax = &quot;proto2&quot; or syntax = &quot;proto3&quot; at the top of proto definition files, you use an edition number, such as edition = &quot;2024&quot;, to specify the default behaviors your file will have.</description></item><item><title>Changes Announced on March 13, 2026</title><link>https://protobuf.dev/news/2026-03-13/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://protobuf.dev/news/2026-03-13/</guid><description>Changes in Bazel Migration of Proto Flags to Starlark --proto_toolchain_for* and --proto_compiler are no longer read by Proto rules. These toolchain-related flags are deprecated and will be removed in the future. Switching to the equivalent Starlark versions of the flags is a short-term fix:
326
+
--@protobuf//bazel/flags/cc:proto_toolchain_for_cc --@protobuf//bazel/flags/java:proto_toolchain_for_java --@protobuf//bazel/flags/java:proto_toolchain_for_javalite --@protobuf//bazel/flags:proto_compiler The longer-term fix is to enable --incompatible_enable_proto_toolchain_resolution (which is the default in Bazel 9 anyway) and to register toolchains using the normal platforms-related mechanisms (register_toolchain() in MODULE.</description></item><item><title>Changes Announced on March 18, 2025</title><link>https://protobuf.dev/news/2025-03-18/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://protobuf.dev/news/2025-03-18/</guid><description>Dropping Ruby 3.0 Support As per our official Ruby support policy, we will be dropping support for Ruby 3.0 and lower in Protobuf version 31, due to release in April, 2025. The minimum supported Ruby version will be 3.1.</description></item><item><title>Changes announced May 6, 2022</title><link>https://protobuf.dev/news/2022-05-06/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://protobuf.dev/news/2022-05-06/</guid><description>Versioning We changed our versioning scheme to enable more-nimble updates to language-specific parts of Protocol Buffers. In the new scheme, each language has its own major version that can be incremented independently of other languages, as covered later in this topic with the Python release. The minor and patch versions, however, will remain coupled. This allows us to introduce breaking changes into some languages without requiring a bump of the major version in languages that do not experience a breaking change.</description></item><item><title>Changes Announced on November 7, 2024</title><link>https://protobuf.dev/news/2024-11-07/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://protobuf.dev/news/2024-11-07/</guid><description>The following sections cover planned breaking changes in the v30 release, expected in 2025 Q1. Also included are some changes that aren&rsquo;t breaking but may require action on your part. These are in addition to those mentioned in the News article from October 2.
326
327
These describe changes as we anticipate them being implemented, but due to the flexible nature of software some of these changes may not land or may vary from how they are described in this topic.</description></item><item><title>Changes Announced on October 1, 2024</title><link>https://protobuf.dev/news/2024-10-01/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://protobuf.dev/news/2024-10-01/</guid><description>Bazel and Proto Rules There are upcoming changes to the way that Bazel will work for protobuf builds. These changes require awareness in the first stage, and action by project owners before the second stage.
327
328
Stage 1 With the release of Bazel 8, proto rules (proto_library, cc_proto_library, java_proto_library, java_lite_proto_library, and py_proto_library) will be removed from the Bazel project. The will be added to the Protocol Buffers project in v29. Bazel will be updated to automatically use the rules from the protobuf project, so the change is initially a no-op for project owners.</description></item><item><title>Changes announced on October 10, 2023</title><link>https://protobuf.dev/news/2023-10-10/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://protobuf.dev/news/2023-10-10/</guid><description>Protobuf Editions Features Documentation that introduces Protobuf Editions features is now available.</description></item><item><title>Changes Announced on October 2, 2024</title><link>https://protobuf.dev/news/2024-10-02/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://protobuf.dev/news/2024-10-02/</guid><description>The following sections cover planned breaking changes in the v30 release, expected in 2025 Q1. These describe changes as we anticipate them being implemented, but due to the flexible nature of software some of these changes may not land or may vary from how they are described in this topic.
328
329
Changes in C++ C++ will bump its major version from 5.29.x to 6.30.x.
@@ -348,4 +349,4 @@ The following sections cover planned breaking changes in the v31 release, expect
348
349
C++ string_type The default for string_type feature, originally released in Edition 2023, will change from STRING to VIEW in Edition 2024.
349
350
See features.(pb.cpp).string_type and String View APIs for more information on this feature and its feature values.
350
351
New Features This section details any new features that will be introduced in Edition 2024.</description></item><item><title>News Announcements for Version 34.x</title><link>https://protobuf.dev/news/v34/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://protobuf.dev/news/v34/</guid><description>The following news topics provide information about changes in the 34.x release.
351
-
January 16, 2026 - Prebuilt proto compiler (protoc) for Bazel September 19, 2025 - Breaking changes in the upcoming 34.x release July 16, 2025 - Resuming support for Bazel with MSVC</description></item></channel></rss>
352
+
March 13, 2026 - Breaking changes in Bazel for the upcoming 34.x release January 16, 2026 - Prebuilt proto compiler (protoc) for Bazel September 19, 2025 - Breaking changes in the upcoming 34.x release July 16, 2025 - Resuming support for Bazel with MSVC</description></item></channel></rss>
0 commit comments