Skip to content

[Snyk] Security upgrade django from 3.2.18 to 4.2.27 - #50

Open
nlaurance wants to merge 1 commit into
masterfrom
snyk-fix-c02a3ffd109b701accda455c133d42ed
Open

nlaurance wants to merge 1 commit into
masterfrom
snyk-fix-c02a3ffd109b701accda455c133d42ed

Conversation

@nlaurance

Copy link
Copy Markdown
Owner

snyk-top-banner

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

Snyk changed the following file(s):

  • requirements/dev.txt

Merge Risk: High

This is a major upgrade from one Long-Term Support (LTS) version of Django to the next, introducing significant breaking changes. Developer action is required.

Key Breaking Changes:

  • Python Support: Support for Python 3.6 and 3.7 has been dropped. Django 4.0 and newer require Python 3.8+. [2, 7]
  • Timezone Handling: The default timezone implementation has switched from pytz to the standard library's zoneinfo. Code using pytz APIs like normalize() or localize() may need to be audited. [2]
  • Database Support: Support for PostgreSQL versions 9.6 and 10 has been dropped. [2, 3]
  • Removed Functions: Deprecated functions like force_text(), smart_text(), and ugettext() have been removed. [2]

Source: Django 4.0 Release Notes
Recommendation: This upgrade requires careful planning. Follow the official "How to upgrade Django" guide, resolve deprecation warnings, and consider an incremental upgrade path (e.g., 3.2 → 4.0 → 4.1 → 4.2) to isolate issues. [9]

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



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:

🦉 SQL Injection

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