From 9fc432f2f5b9040eaf58a0a99e43839282f86682 Mon Sep 17 00:00:00 2001 From: Leandro Lucarella Date: Mon, 5 Oct 2026 14:25:52 +0000 Subject: [PATCH 1/2] Prepare release notes for v0.11.3 Signed-off-by: Leandro Lucarella --- RELEASE_NOTES.md | 10 ++++------ 1 file changed, 4 insertions(+), 6 deletions(-) diff --git a/RELEASE_NOTES.md b/RELEASE_NOTES.md index 62d4e139..3e00ac92 100644 --- a/RELEASE_NOTES.md +++ b/RELEASE_NOTES.md @@ -2,15 +2,13 @@ ## Summary -Fix HTTP/2 keep-alive, which was never actually enabled. +This release adds support for protobuf 7 and fixes HTTP/2 keep-alive, which was +never actually enabled. ## Upgrading - - -## New Features - - +- The protobuf requirement is now `>=5.29.2,<8`, allowing protobuf 7 while + retaining support for protobuf 5 and 6. ## Bug Fixes From 563b1fb6889a7a0757de2fc3acbd71f94adecf53 Mon Sep 17 00:00:00 2001 From: Leandro Lucarella Date: Mon, 5 Oct 2026 18:23:24 +0200 Subject: [PATCH 2/2] Don't wrap lines in release notes RELEASE_NOTES.md is used to create the GitHub release, which renders new lines, making the text flow weird when rendered. Signed-off-by: Leandro Lucarella --- RELEASE_NOTES.md | 16 ++++------------ 1 file changed, 4 insertions(+), 12 deletions(-) diff --git a/RELEASE_NOTES.md b/RELEASE_NOTES.md index 3e00ac92..909152f0 100644 --- a/RELEASE_NOTES.md +++ b/RELEASE_NOTES.md @@ -2,22 +2,14 @@ ## Summary -This release adds support for protobuf 7 and fixes HTTP/2 keep-alive, which was -never actually enabled. +This release adds support for protobuf 7 and fixes HTTP/2 keep-alive, which was never actually enabled. ## Upgrading -- The protobuf requirement is now `>=5.29.2,<8`, allowing protobuf 7 while - retaining support for protobuf 5 and 6. +- The protobuf requirement is now `>=5.29.2,<8`, allowing protobuf 7 while retaining support for protobuf 5 and 6. ## Bug Fixes -- HTTP/2 keep-alive is now actually enabled. `grpc.keepalive_time_ms` and - `grpc.keepalive_timeout_ms` were computed with `timedelta.total_seconds() * 1000` - and therefore passed as `float`. gRPC silently ignores channel arguments that are - neither `int` nor `str`, so no keep-alive pings were ever sent and a client could - only detect a dead stream through its own deadline or a teardown sent by the peer. +- HTTP/2 keep-alive is now actually enabled. `grpc.keepalive_time_ms` and `grpc.keepalive_timeout_ms` were computed with `timedelta.total_seconds() * 1000` and therefore passed as `float`. gRPC silently ignores channel arguments that are neither `int` nor `str`, so no keep-alive pings were ever sent and a client could only detect a dead stream through its own deadline or a teardown sent by the peer. - Note that keep-alive pings are answered by the nearest HTTP/2 peer. Where a proxy - terminates HTTP/2, successful pings prove that hop is alive, not the backend, so - a stream deadline is still needed to detect an orphaned upstream stream. + Note that keep-alive pings are answered by the nearest HTTP/2 peer. Where a proxy terminates HTTP/2, successful pings prove that hop is alive, not the backend, so a stream deadline is still needed to detect an orphaned upstream stream.