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
</span></span></span><spanstyle=display:flex><span><spanstyle=color:#f8f8f8;text-decoration:underline></span><spanstyle=color:#a40000></span><spanstyle=color:#f8f8f8;text-decoration:underline></span><spanstyle=color:#000>stdout</span><spanstyle=color:#000;font-weight:700>.</span><spanstyle=color:#c4a000>println</span><spanstyle=color:#000;font-weight:700>(</span><spanstyle=color:#4e9a06>"Unknown phone type. Using default."</span><spanstyle=color:#000;font-weight:700>);</span><spanstyle=color:#f8f8f8;text-decoration:underline>
327
+
</span></span></span><spanstyle=display:flex><span><spanstyle=color:#f8f8f8;text-decoration:underline></span><spanstyle=color:#000>stdout</span><spanstyle=color:#000;font-weight:700>.</span><spanstyle=color:#c4a000>println</span><spanstyle=color:#000;font-weight:700>(</span><spanstyle=color:#4e9a06>"Unknown phone type. Using default."</span><spanstyle=color:#000;font-weight:700>);</span><spanstyle=color:#f8f8f8;text-decoration:underline>
Copy file name to clipboardExpand all lines: index.xml
+2-1Lines changed: 2 additions & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -328,7 +328,8 @@ After this point, you can continue to use Bazel, or another build system, to bui
328
328
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.
329
329
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.
330
330
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:
331
-
--@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.
331
+
--@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 on May 18, 2026</title><link>https://protobuf.dev/news/2026-05-18/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://protobuf.dev/news/2026-05-18/</guid><description>Dropping support for older versions of .NET As per our official .NET support policy, we will be enforcing the lack of support for .NET 7.0 and lower in the 36.x release.
332
+
The minimum supported .NET version has officially been 8.0 since November 2024 per Foundational .NET Support. 36.x will align our C# project files to match our official support.</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.
332
333
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.
333
334
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.
334
335
Changes in C++ C++ will bump its major version from 5.29.x to 6.30.x.
![copybara-service[bot]](https://avatars.githubusercontent.com/in/44061?v=4&size=40){kind=avatar}
0 commit comments