deploy: e5f9c35

Author: copybara-service[bot]

index.xml

@@ -94,7 +94,8 @@ Note This is a draft spec originally reverse-engineered from the C++ text format
 encoding should be set only to binary, or json, denoting those respective formats. With subtype protobuf+json, encoding has the default json and cannot be set to binary. With subtype protobuf (without +json), encoding has the default binary and cannot be set to json.</description></item><item><title>Protocol Buffers Well-Known Types</title><link>https://protobuf.dev/reference/protobuf/google.protobuf/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://protobuf.dev/reference/protobuf/google.protobuf/</guid><description>Index Any (message) Api (message) BoolValue (message) BytesValue (message) DoubleValue (message) Duration (message) Empty (message) Enum (message) EnumValue (message) Field (message) Field.Cardinality (enum) Field.Kind (enum) FieldMask (message) FloatValue (message) Int32Value (message) Int64Value (message) ListValue (message) Method (message) Mixin (message) NullValue (enum) Option (message) SourceContext (message) StringValue (message) Struct (message) Syntax (enum) Timestamp (message) Type (message) UInt32Value (message) UInt64Value (message) Value (message) Well-Known Types that end in &amp;ldquo;Value&amp;rdquo; are wrapper messages for other types, such as BoolValue and EnumValue.</description></item><item><title>Other Languages</title><link>https://protobuf.dev/reference/other/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://protobuf.dev/reference/other/</guid><description>While the current release includes compilers and APIs for C++, Java, Go, Ruby, C#, and Python, the compiler code is designed so that it&amp;rsquo;s easy to add support for other languages. There are several ongoing projects to add new language implementations to Protocol Buffers, including C, Haskell, Perl, Rust, and more.
 For a list of links to projects we know about, see the third-party add-ons wiki page.
 Compiler Plugins protoc, the Protocol Buffers Compiler, can be extended to support new languages via plugins.</description></item><item><title>Version Support</title><link>https://protobuf.dev/support/version-support/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://protobuf.dev/support/version-support/</guid><description>Support windows for protoc and the various languages are covered in the tables later in this topic. Version numbers throughout this topic use SemVer conventions; in the version &amp;ldquo;3.21.7,&amp;rdquo; we say that &amp;ldquo;3&amp;rdquo; is the major version, &amp;ldquo;21&amp;rdquo; is the minor version, and &amp;ldquo;7&amp;rdquo; is the micro or patch number.
-Starting with the v21.x protoc release, we changed our versioning scheme to enable nimbler updates to language-specific parts of Protocol Buffers.</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.
+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.

reference/rust/rust-generated/index.html

@@ -1,5 +1,6 @@
 <?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Support on Protocol Buffers Documentation</title><link>https://protobuf.dev/support/</link><description>Recent content in Support on Protocol Buffers Documentation</description><generator>Hugo</generator><language>en</language><atom:link href="https://protobuf.dev/support/index.xml" rel="self" type="application/rss+xml"/><item><title>Version Support</title><link>https://protobuf.dev/support/version-support/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://protobuf.dev/support/version-support/</guid><description>Support windows for protoc and the various languages are covered in the tables later in this topic. Version numbers throughout this topic use SemVer conventions; in the version &amp;ldquo;3.21.7,&amp;rdquo; we say that &amp;ldquo;3&amp;rdquo; is the major version, &amp;ldquo;21&amp;rdquo; is the minor version, and &amp;ldquo;7&amp;rdquo; is the micro or patch number.
-Starting with the v21.x protoc release, we changed our versioning scheme to enable nimbler updates to language-specific parts of Protocol Buffers.</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.
+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.