upgrade to django 4.2.14 (from 2.2.20) #81
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
aarushtools
force-pushed
the
upgrade-django
branch
4 times, most recently
from
9391fdc
to
ccce200
Compare
There was a problem hiding this comment.
Hello! Just noticed some stuff while looking through...
About #79, I'm a little bit busy this week, and I still need to upgrade Flask on that PR. Seeing as this PR is almost done, I would prefer to get this PR merged before mine :)
aarushtools
force-pushed
the
upgrade-django
branch
from
ccce200
to
5d93ab8
Compare
aarushtools
force-pushed
the
upgrade-django
branch
from
5d93ab8
to
e26f72f
Compare
aarushtools
force-pushed
the
upgrade-django
branch
from
e26f72f
to
fc7303f
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.
Rationale
Changes
Important
#79 will need to have merge conflicts resolved after this PR is merged