Merged
Conversation
cffe090 to
fa7c204
Compare
c9da5c5 to
44f6148
Compare
2294362 to
882aaad
Compare
8641710 to
b1e2da4
Compare
rafiss
approved these changes
Dec 4, 2025
| @@ -1,14 +1,6 @@ | |||
| # Changelog | |||
|
|
|||
| ## 5.2.1 - Unreleased | |||
Contributor
There was a problem hiding this comment.
should we create a separate branch for Django 5.2 support, and make a release from there? (separately from this PR)
Collaborator
Author
There was a problem hiding this comment.
Yes, there are stable branches in case we need to backport any critical fixes. I made the 5.2.1 release.
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.
Django 6.0 was released December 3, 2025.