Repository navigation
docs: pre-release correctness pass for 0.4.0 - #429
Merged
Merged
Conversation
- migration guide: drop pre-release wording, fix the use_bearer_token and get_or_set lock snippets, date the CacheError and UserSessionDep notes - changelog: release notice, entries for the session changes 0.3.9 announced but 0.4.0 does not make (#75, #131, #377), migration links - SECURITY.md: 0.4.x is the supported line - HTTP caching, backends, lock and app cache pages: deprecation context for sessions, ttl in the normal-caching examples, smaller corrections - zh-TW follows, plus glossary fixes
…col, zh punctuation)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
A correctness pass over the docs before 0.4.0, checking each statement against the code.
[Unreleased]pointing to the migration guide and the session/state deprecation. New fragments record that three session changes announced in 0.3.9 are not made (Allow cookies in token_source_priority #75, 0.4.0: resolveget_session_managerthroughSessionManagerProxy#131, 0.4.0: remove SessionConfig.use_bearer_token in favour of token_source_priority #377).use_bearer_token=False,UserSessionDepand theCacheErrorwarning history. Theget_or_setlock example now usesCacheManager(lock=False). "Dropped" rows are marked as needing no action.http:v2|…key format,RedisConfigvalidation, Memcachedclear()warnings,CacheLock.acquire()defaults and session deprecation context in line with the code.Merge timing: SECURITY.md declares 0.3.9 unsupported and promises fixes as 0.4.x patches, so this PR should merge immediately before the 0.4.0 release, not earlier. The
[Unreleased]notice and fragments link to/en/stable/anchors that exist only once 0.4.0 is the stable docs.An independent review agent checked the diff against the code before this PR; its findings are applied in the last commit.