Update to Django 6.0 #280
Draft
Update to Django 6.0 #280
+61
−17
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
timgraham
force-pushed
the
django60
branch
2 times, most recently
from
3b8b13b to
6dacd76
Compare
timgraham
force-pushed
the
django60
branch
2 times, most recently
from
22f82c1 to
329b2b7
Compare
timgraham
force-pushed
the
django60
branch
2 times, most recently
from
923146b to
757ce75
Compare
timgraham
force-pushed
the
django60
branch
2 times, most recently
from
54c1059 to
306f2d6
Compare
timgraham
force-pushed
the
django60
branch
3 times, most recently
from
3a27a24 to
8c303ca
Compare
timgraham
force-pushed
the
django60
branch
3 times, most recently
from
8087b67 to
bec0ec5
Compare
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 will be released December 2025.
This is to check compatibility in the meantime.