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
Copy file name to clipboardExpand all lines: CHANGELOG.md
+59Lines changed: 59 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,3 +1,62 @@
1
+
### v1.8.1 (2025-11-13)
2
+
3
+
4
+
#### Bug Fixes
5
+
6
+
***http1:** fix consuming extra CPU from previous change (#3977) ([4492f31e](https://github.com/hyperium/hyper/commit/4492f31e9429c34166da5a069c00b65be20e4a02))
7
+
8
+
9
+
## v1.8.0 (2025-11-11)
10
+
11
+
12
+
#### Bug Fixes
13
+
14
+
***http1:** fix rare missed write wakeup on connections (#3952) ([2377b893](https://github.com/hyperium/hyper/commit/2377b893f6e64ca9878e4f25d1472b96baa7e3ea))
***rt:** add `Timer::now()` method to allow overriding the instant returned (#3965) ([5509ebe6](https://github.com/hyperium/hyper/commit/5509ebe6156e32d4f8986fafa25c2918a30005be))
21
+
22
+
23
+
#### Breaking Changes
24
+
25
+
* The HTTP/2 client connection no longer allows an executor
26
+
that can not spawn itself.
27
+
28
+
This was an oversight originally. The client connection will now include spawning
29
+
a future that keeps a copy of the executor to spawn other futures. Thus, if it is
30
+
`!Send`, it needs to spawn `!Send` futures. The likelihood of executors that match
31
+
the previously allowed behavior should be very remote.
32
+
33
+
There is also technically a semver break in here, which is that the
34
+
`Http2ClientConnExec` trait no longer dyn-compatible, because it now expects to
35
+
be `Clone`. This should not break usage of the `conn` builder, because it already
36
+
separately had `E: Clone` bounds. If someone were using `dyn Http2ClientConnExec`,
37
+
that will break. However, there is no purpose for doing so, and it is not usable
38
+
otherwise, since the trait only exists to propagate bounds into hyper. Thus, the
***server:** improve caching accuracy of Date header (#3887) ([436cadd1](https://github.com/hyperium/hyper/commit/436cadd1ac08a9508a46f550e03281db9f2fee97))
49
+
50
+
51
+
#### Features
52
+
53
+
***client:**
54
+
* add a `TrySendError::error()` method (#3885) ([efa0b269](https://github.com/hyperium/hyper/commit/efa0b26958386ffaf646e6d9a3150ca5041162a3))
55
+
* add a `TrySendError::message()` method (#3884) ([03fd6aff](https://github.com/hyperium/hyper/commit/03fd6aff88c99a0842bb2e578a4993a432c03049))
hyper (and related projects in hyperium) use the same security policy as the [Tokio project][tokio-security].
3
+
hyper (and related projects in hyperium) take security seriously, and greatly appreciate responsibile disclosure.
4
4
5
5
## Report a security issue
6
6
7
-
The process for reporting an issue is the same as the [Tokio project][tokio-security]. This includes private reporting via [email protected].
7
+
To report a security issue in hyper, or another crate in the hyperium organization, please [report a new draft GitHub Security Advisory](https://github.com/hyperium/hyper/security/advisories/new).
We will discuss it privately with you. hyper maintainers will determine the impact and release details. Participation in security issue coordination is at the discretion of hyper maintainers.
10
+
11
+
## Transparency
12
+
13
+
We are committed to transparency in the security issue disclosure process. Advisories will be disclosed publicly once a patch is released, and if appropriate, added to the RustSec advisory database.
0 commit comments