-
Notifications
You must be signed in to change notification settings - Fork 59
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
Drop support for Wagtail < 4.1 #314
Conversation
3753d34
to
943eb85
Compare
aa903bc
to
8085d79
Compare
- python-version: '3.11' | ||
wagtail-version: 'main' | ||
allowfail: true |
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 dig this allow-fail setup. I may need to consider for some other projects.
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.
got that idea from actions/runner#2347
the UI will still be clunky (is it shows a red x like other fails).
I aim to move this to a nightly job as part of #289
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.
Cool.. I like having the canary for upcoming releases... but I think I'm in agreement wrt not wanting the big red x against unreleased code to be a distraction.
* Change to support Wagtail 4.1+ and Python 3.8+ * Drop pre-4.1 shims * Remove unused code * Update CI * Use python 3.10 for RTD https://docs.readthedocs.io/en/stable/tutorial/index.html#upgrading-the-python-version https://docs.readthedocs.io/en/stable/config-file/v2.html#python * Update docs theme
4.1 is the latest LTS.
With 4.2 out, 2.15 (the previous LTS) no longer receives updates.
Time to tidy up. While at it, dropped Python 3.7 support