From be57d62a8a308442343e761f0fe9586bbbec1601 Mon Sep 17 00:00:00 2001 From: allen0099 Date: Tue, 29 Sep 2026 08:40:13 +0000 Subject: [PATCH] docs(changelog): correct the warning claims in the #126 and #256 fragments --- changelog.d/126.deprecated.md | 10 ++++++---- changelog.d/256.deprecated.md | 6 +++--- 2 files changed, 9 insertions(+), 7 deletions(-) diff --git a/changelog.d/126.deprecated.md b/changelog.d/126.deprecated.md index bf9f343..c973fae 100644 --- a/changelog.d/126.deprecated.md +++ b/changelog.d/126.deprecated.md @@ -1,5 +1,7 @@ **The `encoding` option of `AsyncRedisCacheBackend` and `RedisConfig`.** 0.4.0 -removes it and reads raw bytes; entries were always UTF-8. Passing `encoding` -to `AsyncRedisCacheBackend`, or setting it on a `RedisConfig` given to -`load_from_config()`, now emits a `DeprecationWarning`. Leave it out: UTF-8 is -what you get without it. A value other than UTF-8 keeps its `RuntimeWarning`. +removes it and reads raw bytes; entries were always UTF-8. Passing a UTF-8 +`encoding` to `AsyncRedisCacheBackend`, or setting `encoding` on a +`RedisConfig` given to `load_from_config()`, now emits a `DeprecationWarning`. +Any other value passed to `AsyncRedisCacheBackend` gets no +`DeprecationWarning`: it keeps its `RuntimeWarning`, which already announces the +removal. Leave it out: UTF-8 is what you get without it. diff --git a/changelog.d/256.deprecated.md b/changelog.d/256.deprecated.md index 8d3e329..6a4429e 100644 --- a/changelog.d/256.deprecated.md +++ b/changelog.d/256.deprecated.md @@ -4,6 +4,6 @@ default, so every cookie session is logged out once on upgrade and a plain-HTTP setup stops receiving the cookie. The middleware now emits a `FutureWarning` when its config leaves `cookie_name` or `cookie_https_only` at the default. Set both: `cookie_name="session", cookie_https_only=False` keeps the current cookie, -`cookie_name="__Host-session", cookie_https_only=True` switches now. Header-only -setups never send the cookie and do not warn. See "Migrating to 0.4.0" in the -docs. +`cookie_name="__Host-session", cookie_https_only=True` switches now. The +warning does not depend on how clients send the token: a header-only app on +this middleware warns too. See "Migrating to 0.4.0" in the docs.