Skip to content
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

Upgrade wagtail support to anything in this major version #38

Merged
merged 2 commits into from
Dec 3, 2020

Conversation

alexm118
Copy link
Contributor

@alexm118 alexm118 commented Dec 3, 2020

Configures our testing suite to test against the latest release of wagtail instead of a hard set maximum.

Changes

  • wagtail < 2.11 -> wagtail < 3

Notes

  • This is to align with our new goal of supporting new releases of wagtail based on tests passing, rather than manually confirming the library works.

Checklist

  • PR has an informative and human-readable title
  • Changes are limited to a single goal (no scope creep)
  • Code can be automatically merged (no conflicts)
  • Code follows the standards laid out in the development playbook
  • Passes all existing automated tests
  • Any change in functionality is tested
  • New functions are documented (with a description, list of inputs, and expected output)
  • Placeholder code is flagged / future todos are captured in comments
  • Visually tested in supported browsers and devices (see checklist below 👇)
  • Project documentation has been updated (including the "Unreleased" section of the CHANGELOG)
  • Reviewers requested with the Reviewers tool ➡️

@alexm118 alexm118 merged commit 34c9df9 into main Dec 3, 2020
@alexm118 alexm118 deleted the wagtail-upgrade branch December 3, 2020 20:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants