uplift to Wagtail 2.2.2 on Django 2.0.9 #3031
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
…2.7.7 because 2.8 is Django-breaking
cadecairos
approved these changes
Apr 18, 2019
Pomax
added a commit
that referenced
this pull request
Apr 22, 2019
Builds on #3031 by uplifting wagtail to 2.3 and Django to 2.1.1
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.
And with
psycopg2forced down to 2.7.7 because 2.8 is Django-breaking... yay!Supercedes #2993?
Related PRs/issues #2993
This is part 1 of a multi-step uplift, because going from wagtail 2.1.3 straight to 2.4 apparently doesn't work, so we need to go 2.1.3 (our master) => 2.2.2 (this PR) => 2.3 (#3032) => 2.4 (#3033)
Note that we will also have to prod push this "in order", so some care will have to be taken there.