[Snyk] Security upgrade wagtail from 5.0.5 to 7.0.8

[robertatakenaka]

Snyk has created this PR to fix 1 vulnerabilities in the pip dependencies of this project.

Snyk changed the following file(s):

• requirements/base.txt

⚠️ Warning

flower 2.0.1 requires tornado, which is not installed.
celery 5.3.0 requires kombu, which is not installed.

Breaking Change Risk

Notice: This assessment is enhanced by AI.

---

Important

• Check the changes in this PR to ensure they won't cause issues with your project.
• Max score is 1000. Note that the real score may have changed since the PR was raised.
• This PR was automatically created by Snyk using the credentials of a real user.
• Some vulnerabilities couldn't be fully fixed and so Snyk will still find them when the project is tested again. This may be because the vulnerability existed within more than one direct dependency, but not all of the affected dependencies could be upgraded.

---

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic

---

Learn how to fix vulnerabilities with free interactive lessons:

🦉 Cross-site Scripting (XSS)

[robertatakenaka]

This is a major upgrade from Wagtail 5.x to 7.x, which includes multiple significant and breaking changes. A direct upgrade is not recommended; the official guidance is to upgrade one feature release at a time to manage deprecation warnings and database migrations. [6, 14]

Key Breaking Changes:

Wagtail 6.0:

• Python/Django Version: Support for Django versions below 4.2 has been removed. You must upgrade to at least Django 4.2 before upgrading to Wagtail 6.0. [3]
• Elasticsearch: Support for Elasticsearch 5 and 6 has been dropped. If you use Elasticsearch, you must upgrade to version 7 or 8. [3]
• Removed Features: Features that were deprecated in Wagtail versions 4.2, 5.0, and 5.1 have been removed. [3]

Wagtail 7.0:

• Removed/Renamed APIs: This version removes features deprecated between versions 5.2 and 6.3. [11] Notable changes include:
  • The classnames attribute on MenuItem and image.Format classes is replaced with classname. [11]
  • The WAGTAIL_AUTO_UPDATE_PREVIEW setting is removed and replaced by WAGTAIL_AUTO_UPDATE_PREVIEW_INTERVAL. [11]
• Behavioral Change: Validation on required fields is now deferred by default when saving drafts and is only enforced on publish. This is a significant change to the content editing workflow. [2, 4]
• UI Changes: A new pagination interface is used in admin listings and choosers, which may affect custom admin templates. [2]

Recommendation: This upgrade requires significant developer action. Do not merge without a careful, staged upgrade process. Review the release notes for each intermediate version between 5.0 and 7.0 to identify all deprecated features that need to be refactored in your project.

Notice 🤖: This content was augmented using artificial intelligence. AI-generated content may contain errors and should be reviewed for accuracy before use.