Skip to content

Commit 5028705

Browse files
committed
Bump patch version.
1 parent f25091d commit 5028705

File tree

3 files changed

+6
-6
lines changed

3 files changed

+6
-6
lines changed

lib/async/http/version.rb

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -7,6 +7,6 @@
77
module Async
88
# @namespace
99
module HTTP
10-
VERSION = "0.94.2"
10+
VERSION = "0.94.3"
1111
end
1212
end

readme.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -16,6 +16,10 @@ Please see the [project documentation](https://socketry.github.io/async-http/) f
1616

1717
Please see the [project releases](https://socketry.github.io/async-http/releases/index) for all releases.
1818

19+
### v0.94.3
20+
21+
- Fix response body leak in HTTP/2 server when stream is reset before `send_response` completes (e.g. client-side gRPC cancellation). The response body's `close` was never called, leaking any resources tied to body lifecycle (such as `rack.response_finished` callbacks and utilization metrics).
22+
1923
### v0.94.1
2024

2125
- Fix `defer_stop` usage in `HTTP1::Server`, improving server graceful shutdown behavior.
@@ -52,10 +56,6 @@ Please see the [project releases](https://socketry.github.io/async-http/releases
5256

5357
- Add support for HTTP/2 `NO_RFC7540_PRIORITIES`. See <https://www.rfc-editor.org/rfc/rfc9218.html> for more details.
5458

55-
### v0.84.0
56-
57-
- Minor consistency fixes to `Async::HTTP::Internet` singleton methods.
58-
5959
## See Also
6060

6161
- [benchmark-http](https://github.com/socketry/benchmark-http) — A benchmarking tool to report on web server concurrency.

releases.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
# Releases
22

3-
## Unreleased
3+
## v0.94.3
44

55
- Fix response body leak in HTTP/2 server when stream is reset before `send_response` completes (e.g. client-side gRPC cancellation). The response body's `close` was never called, leaking any resources tied to body lifecycle (such as `rack.response_finished` callbacks and utilization metrics).
66

0 commit comments

Comments
 (0)