Found new managed modules references

[app-token-modules]

No description provided.

[github-actions]

[Posted at 2026-09-03T12:14:08Z]

Intermediate transition

$ casdiff 99135b19189588fcc787acb84cff27991787473d \
          dd549fc4ed04b60b0fdd3866b82ef0a7c87c6e4f \
          --format=markdown

3 files changed: 0 removed, 0 renamed, 0 added, 3 changed content.

3 files changed: 0 removed, 0 renamed, 0 added, 3 changed content.

Files changed content:

buf.md:

--- shake256:3736ab9625deb2a2e1f50c338c9f43112f275819b3914dba6f1ef48c6fb8bf4df43172eef656ea808a786df5278b9d822378931a8b6c42ebef6d07c2f52732c9  buf.md
+++ shake256:0dd5aee9d5e074a94178298d5098f1820b8c6900612021292a8617546c4e2bf1bff3c6740465d6cf51294bec2d606f63f2bc731384d0a3616fbf467396737667  buf.md
@@ -8,7 +8,7 @@
 
 ```
 deps:
-  - buf.build/grpc/grpc:<GIT_COMMIT_TAG>
+  - {{bsrhost}}/grpc/grpc:<GIT_COMMIT_TAG>
 ```
 
 For more information, see the [documentation](https://buf.build/docs/bsr/overview).

grpc/binlog/v1/binarylog.proto:

--- shake256:ecdc715885fffb15f278a7c379bde153bb29c6fd3b4c9b38459d710879802ab35f4e306ebe9193d35841f43edfbd3722198507393406daefdd5e4a09dcf28af2  grpc/binlog/v1/binarylog.proto
+++ shake256:9e87c82b2d6c5daf2d052630f8fe46be9cb764a3a2821fa6a0941bf59970aead412ed5a5969fda05841681c9dede5b36f1f4191a2073ed1446c18cf50527bd2c  grpc/binlog/v1/binarylog.proto
@@ -162,7 +162,7 @@
 // A list of metadata pairs, used in the payload of client header,
 // server header, and server trailer.
 // Implementations may omit some entries to honor the header limits
-// of GRPC_BINARY_LOG_CONFIG.
+// of GRPC_BINARY_LOG_FILTER.
 //
 // Header keys added by gRPC are omitted. To be more specific,
 // implementations will not log the following entries, and this is
@@ -172,7 +172,9 @@
 //   or keys like 'lb-token'
 // - transport specific entries, including but not limited to:
 //   ':path', ':authority', 'content-encoding', 'user-agent', 'te', etc
-// - entries added for call credentials
+// - entries added for call credentials (on client side, excludes all
+//   such headers; on server side, excludes only the "authorization"
+//   header)
 //
 // Implementations must always log grpc-trace-bin if it is present.
 // Practically speaking it will only be visible on server side because

grpc/binlog/v1alpha/binarylog.proto:

--- shake256:5812652254993cb9b622e0bfce96840041b9571b1c969c4ee4fbdf8ffe409965fa1f1dc8f8243e38b5a8e91cdfa92cf7d297ad4b625790ada0a3abb0d0822951  grpc/binlog/v1alpha/binarylog.proto
+++ shake256:efdee8caaa1ef1c4062a44845094df509cd9aa8b5faec92ac1cb2646abb4952503d62396f8aca60eac61cd04e33024933dca2e7d12e3e945bb6140503234d73a  grpc/binlog/v1alpha/binarylog.proto
@@ -119,7 +119,7 @@
 // A list of metadata pairs, used in the payload of CLIENT_INIT_METADATA,
 // SERVER_INIT_METADATA and TRAILING_METADATA
 // Implementations may omit some entries to honor the header limits
-// of GRPC_BINARY_LOG_CONFIG.
+// of GRPC_BINARY_LOG_FILTER.
 // 
 // Implementations will not log the following entries, and this is
 // not to be treated as a truncation:
@@ -127,7 +127,9 @@
 //   that begin with 'grpc-' or keys like 'lb-token'
 // - transport specific entries, including but not limited to:
 //   ':path', ':authority', 'content-encoding', 'user-agent', 'te', etc
-// - entries added for call credentials
+// - entries added for call credentials (on client side, excludes all
+//   such headers; on server side, excludes only the "authorization"
+//   header)
 message Metadata {
   repeated MetadataEntry entry = 1 [deprecated = true];
 }

[github-actions]

[Posted at 2026-09-03T12:14:09Z]

Overall transition

$ casdiff 99135b19189588fcc787acb84cff27991787473d \
          dd549fc4ed04b60b0fdd3866b82ef0a7c87c6e4f \
          --format=markdown

3 files changed: 0 removed, 0 renamed, 0 added, 3 changed content.

Files changed content:

buf.md:

--- shake256:3736ab9625deb2a2e1f50c338c9f43112f275819b3914dba6f1ef48c6fb8bf4df43172eef656ea808a786df5278b9d822378931a8b6c42ebef6d07c2f52732c9  buf.md
+++ shake256:0dd5aee9d5e074a94178298d5098f1820b8c6900612021292a8617546c4e2bf1bff3c6740465d6cf51294bec2d606f63f2bc731384d0a3616fbf467396737667  buf.md
@@ -8,7 +8,7 @@
 
 ```
 deps:
-  - buf.build/grpc/grpc:<GIT_COMMIT_TAG>
+  - {{bsrhost}}/grpc/grpc:<GIT_COMMIT_TAG>
 ```
 
 For more information, see the [documentation](https://buf.build/docs/bsr/overview).

grpc/binlog/v1/binarylog.proto:

--- shake256:ecdc715885fffb15f278a7c379bde153bb29c6fd3b4c9b38459d710879802ab35f4e306ebe9193d35841f43edfbd3722198507393406daefdd5e4a09dcf28af2  grpc/binlog/v1/binarylog.proto
+++ shake256:9e87c82b2d6c5daf2d052630f8fe46be9cb764a3a2821fa6a0941bf59970aead412ed5a5969fda05841681c9dede5b36f1f4191a2073ed1446c18cf50527bd2c  grpc/binlog/v1/binarylog.proto
@@ -162,7 +162,7 @@
 // A list of metadata pairs, used in the payload of client header,
 // server header, and server trailer.
 // Implementations may omit some entries to honor the header limits
-// of GRPC_BINARY_LOG_CONFIG.
+// of GRPC_BINARY_LOG_FILTER.
 //
 // Header keys added by gRPC are omitted. To be more specific,
 // implementations will not log the following entries, and this is
@@ -172,7 +172,9 @@
 //   or keys like 'lb-token'
 // - transport specific entries, including but not limited to:
 //   ':path', ':authority', 'content-encoding', 'user-agent', 'te', etc
-// - entries added for call credentials
+// - entries added for call credentials (on client side, excludes all
+//   such headers; on server side, excludes only the "authorization"
+//   header)
 //
 // Implementations must always log grpc-trace-bin if it is present.
 // Practically speaking it will only be visible on server side because

grpc/binlog/v1alpha/binarylog.proto:

--- shake256:5812652254993cb9b622e0bfce96840041b9571b1c969c4ee4fbdf8ffe409965fa1f1dc8f8243e38b5a8e91cdfa92cf7d297ad4b625790ada0a3abb0d0822951  grpc/binlog/v1alpha/binarylog.proto
+++ shake256:efdee8caaa1ef1c4062a44845094df509cd9aa8b5faec92ac1cb2646abb4952503d62396f8aca60eac61cd04e33024933dca2e7d12e3e945bb6140503234d73a  grpc/binlog/v1alpha/binarylog.proto
@@ -119,7 +119,7 @@
 // A list of metadata pairs, used in the payload of CLIENT_INIT_METADATA,
 // SERVER_INIT_METADATA and TRAILING_METADATA
 // Implementations may omit some entries to honor the header limits
-// of GRPC_BINARY_LOG_CONFIG.
+// of GRPC_BINARY_LOG_FILTER.
 // 
 // Implementations will not log the following entries, and this is
 // not to be treated as a truncation:
@@ -127,7 +127,9 @@
 //   that begin with 'grpc-' or keys like 'lb-token'
 // - transport specific entries, including but not limited to:
 //   ':path', ':authority', 'content-encoding', 'user-agent', 'te', etc
-// - entries added for call credentials
+// - entries added for call credentials (on client side, excludes all
+//   such headers; on server side, excludes only the "authorization"
+//   header)
 message Metadata {
   repeated MetadataEntry entry = 1 [deprecated = true];
 }