[Django 4.2]: Upgrade Django to 4.2 #673
Merged
Conversation
This file contains 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
iamsobanjaved
force-pushed
the
django42
branch
from
3f2297a to
77b0e18
Compare
irtazaakram
force-pushed
the
django42
branch
from
0ee84c8 to
66785ae
Compare
iamsobanjaved
force-pushed
the
django42
branch
from
1aec6b3 to
737e225
Compare
macdiesel
approved these changes
Oct 3, 2023
|
Need this to be merged before this PR |
irfanuddinahmad
pushed a commit
that referenced
this pull request
Jul 24, 2024
[Django 4.2]: Upgrade Django to 4.2
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.
Description
Upgrading to django42 and dropped django32 support.
Ticket Link
Owning team or SRE can confirm mysql8.
Related PR
Post-review