Skip to content

docs(changelog): correct the warning claims in the #126 and #256 fragments - #369

Merged
allen0099 merged 1 commit into
masterfrom
docs/changelog-fragment-wording
Sep 29, 2026
Merged

allen0099 merged 1 commit into
masterfrom
docs/changelog-fragment-wording

Conversation

@allen0099

Copy link
Copy Markdown
Owner

Two 0.3.9 changelog fragments describe warnings that the code does not emit that way. Both go into the 0.3.9 CHANGELOG and release notes as written, so they should be fixed before the release.

  • changelog.d/256.deprecated.md said "Header-only setups never send the cookie and do not warn". FastAPICacheXSessionMiddleware warns whenever cookie_name or cookie_https_only is left at the default, however clients send the token. The sentence now says so.
  • changelog.d/126.deprecated.md said that passing encoding to AsyncRedisCacheBackend emits a DeprecationWarning. Only a UTF-8 value does. Any other value gets only the existing RuntimeWarning, which already announces the removal. Setting encoding on a RedisConfig given to load_from_config() warns for any value, as before.

Changelog fragments only; no code changes. Found during the docs audit (#359–#361, #367).

@allen0099 allen0099 added documentation Improvements or additions to documentation backends Cache backends and their atomic primitives session Session management subsystem labels Sep 29, 2026
@allen0099
allen0099 merged commit 269f869 into master Sep 29, 2026
11 checks passed
@allen0099
allen0099 deleted the docs/changelog-fragment-wording branch September 29, 2026 08:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backends Cache backends and their atomic primitives documentation Improvements or additions to documentation session Session management subsystem

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant