Add support for Wagtail 2.16 and Django 4.0 #56
Merged
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.
This commit adds support for Wagtail version
3.02.16 and Django version 4.0, while still maintaining support for all previous versions. This supersedes #54.To comply with the Django 3.2 recommendation around use of BigAutoField for model primary keys, a migration has been added that alters the type of the PageBlock primary key to this type.
Automatic testing of Wagtail 2.16 has been dropped in favor of testing against Wagtail 3.0. Note that this PR currently hardcodes a pre-release version of Wagtail (Edited: I've retarted this PR to Wagtail 2.16 per #54 (comment).3.0rc3
) for testing purposes. This should be updated to a valid release range once 3.0 is released next week.