-
Notifications
You must be signed in to change notification settings - Fork 17
Wagtail 50 #20
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
base: master
Are you sure you want to change the base?
Wagtail 50 #20
Conversation
- name: Test with tox | ||
id: test-with-tox | ||
run: | | ||
tox |
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.
Thank you for adding this
py{38,39,310}-dj{32,40}-wt{216,30,40} | ||
py{39,310}-dj{41}-wt{40,41} | ||
py{38,39,310}-dj{32,41,42}-wt{41,42,50} | ||
py{311}-dj{41,42}-wt{41,42,50} |
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.
If this can be condensed, this is good, but for some reason, it fails for me in another package:
https://github.com/katdom13/wagtailmenus/actions/runs/5217610335/jobs/9417615529
it seems like Wagtail 4.1 and 4.2 don't really support Django 4.2
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.
@katdom13 You are right, I made a change thanks.
Hi @nickmoreton , LGTM, |
you might wanna consider changing the requirement of wagtail.contrib.modeladmin since it's now deprecated. |
Hi @nickmoreton , |
This updates the package for Wagtail 5.0 support.
Support ticket: https://torchbox.monday.com/boards/1124794299/pulses/1131920812
There's no reason the package wouldn't work on versions since 4.1
This adds some testing for the latest version of Django and Wagtail
This builds on PR: #19