Update Django documentation links to use stable version #9698
Conversation
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
Replace old /en/dev/ Django docs links with /en/stable/ equivalents in the caching apiguide
|
All outdated Django documentation links have been updated to use the stable version, except the [JSONField] link in the API guide filtering topic. |
Co-authored-by: Bruno Alla <browniebroke@users.noreply.github.com>
auvipy
approved these changes
May 13, 2025
ulgens
approved these changes
May 13, 2025
browniebroke
approved these changes
May 13, 2025
|
Thanks! |
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.
Replaced old Django documentation links that pointed to "dev", "2.0", "3.0", and "4.0" versions with links to the "stable" version.
This ensures that readers always see stable and supported Django documentation instead of older and outdated versions. Updates were made in various topics in the API guide.