-
Notifications
You must be signed in to change notification settings - Fork 44
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update for Wagtail 6.3 #96
Conversation
add Wagtail 6.3 and drop no longer supported Wagtail versions from the tox matrix
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just one suggestion from me. Thanks @JakubMastalerz
.github/workflows/python-tox.yml
Outdated
@@ -8,7 +8,7 @@ jobs: | |||
|
|||
strategy: | |||
matrix: | |||
python-version: ["3.8", "3.9", "3.10", "3.11", "3.12"] | |||
python-version: ["3.8", "3.9", "3.10", "3.11", "3.12", "3.13"] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
python-version: ["3.8", "3.9", "3.10", "3.11", "3.12", "3.13"] | |
python-version: ["3.9", "3.10", "3.11", "3.12", "3.13"] |
We probably don't need 3.8 any longer
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I wasn't sure about this. On one hand, python 3.8 has reached end-of-life. On the other, it is listed as compatible with Wagtail 5.2. My instinct was to wait until 5.2 becomes deprecated to remove it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Dropped 3.8 in a685634
Update package for Wagtail 6.3
This PR updates the tox testing setup to account for the Wagtail 6.3 release by: