Version bumps: Django 2.1.13, Wagtail 2.3, Pillow 5.4.1 #22
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
|
Thanks! |
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.
Upgrading Wagtail to v2.3. I recall some Django version issues around this time, so I pinned Django to 2.1.13 and will update Django as Wagtail gets updated.
There was a Pillow warning. Pillow 6.2.0 was being installed but
<6.0was required for Wagtail 2.3, so I pinned the latest accepted version of Pillow which was5.4.1.Running the site locally seemed to work fine for me, but I'm not sure if there's a preferred way to test a production-like site just to check. It'd be great if someone else could also make sure the requirements don't break wagtail.io before deploying.