[Snyk] Fix for 5 vulnerabilities

[rondinelisaad]

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

Snyk changed the following file(s):

• requirements/base.txt

⚠️ Warning

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)

[rondinelisaad]

This update includes major version upgrades for wagtail and pillow, introducing significant breaking changes and requiring careful migration.

wagtail@5.0.5 → wagtail@7.0.8

Risk: HIGH

This is a major upgrade across two significant versions (5.x → 7.x) and is considered high-risk. Wagtail documentation strongly recommends upgrading one feature release at a time rather than making a large jump. This upgrade will require significant developer action and testing.

Key Breaking Changes:

• Wagtail 6.0:
  • ModelAdmin Removed: The ModelAdmin feature has been completely removed from Wagtail core and is now available as a separate external package. Projects relying on ModelAdmin will need to integrate this new package or refactor to use Snippets.
  • Django Version: Support for Django versions older than 4.2 has been dropped. Your project must be upgraded to at least Django 4.2.
  • Elasticsearch Version: Support for Elasticsearch 5 and 6 has been removed. An upgrade to Elasticsearch 7 or 8 is required.
  • Universal Listings: A new unified interface for listings (Pages, Snippets, Forms) was introduced, which may affect custom admin interfaces.
• Wagtail 7.0:
  • LTS Release & Django 5.2 Support: This is a Long-Term Support (LTS) release and adds compatibility with Django 5.2.
  • Deferred Draft Validation: The validation behavior for saving drafts has changed. Required fields are generally not enforced when saving a draft, which could alter custom validation logic.
  • Removal of Deprecated Features: Features deprecated in versions 5.2 through 6.3 have been removed.

Recommendation: Do not merge this upgrade directly. Create a dedicated plan to upgrade Wagtail incrementally, version by version (e.g., 5.0 → 5.1 → 5.2 → 6.0 ...), addressing deprecation warnings and breaking changes at each step.

pillow@9.5.0 → pillow@12.3.0

Risk: MEDIUM

This upgrade spans three major versions (10.0.0, 11.0.0, 12.0.0) and includes breaking changes, primarily related to environment support and the removal of deprecated APIs.

Key Breaking Changes:

• Python Support Dropped:
  • v10.0.0 dropped support for Python 3.7.
  • v11.0.0 dropped support for Python 3.8.
  • v12.0.0 dropped support for Python 3.9.
• API Removals:
  • v10.0.0: Several deprecated constants and functions were removed, most notably Image.ANTIALIAS, which must be replaced with Image.Resampling.LANCZOS. Other removals include im.category and JpegImagePlugin.convert_dict_qtables.
  • v11.0.0: The internal PSFile class and PyAccess were removed.
  • v12.0.0: Internal helper functions like ImageFile.raise_oserror and IptcImageFile functions were removed.

Recommendation: Verify that your project's Python environment is compatible (Python 3.10+). Review your codebase for usage of removed constants like Image.ANTIALIAS and update them according to the Pillow migration guide.

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