Skip to content

[Snyk] Security upgrade django from 1.2 to 4.2.26#41

Open
hsingh23 wants to merge 1 commit intomasterfrom
snyk-fix-6e767ed574cc531817429ee606f5b59a
Open

[Snyk] Security upgrade django from 1.2 to 4.2.26#41
hsingh23 wants to merge 1 commit intomasterfrom
snyk-fix-6e767ed574cc531817429ee606f5b59a

Conversation

@hsingh23
Copy link
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.txt

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

Copy link

@chatgpt-codex-connector chatgpt-codex-connector bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment on lines 6 to 8
# GAE packages should match the "libraries" section of app.yaml
django==1.2
django==4.2.26
jinja2==2.6

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P0 Badge Upgrading to Django 4 breaks Python 2 environment

Bumping django to 4.2.26 assumes a Python ≥3.8 runtime, while the project still targets the legacy App Engine Python runtime (app.yaml declares runtime: python and the surrounding pinned packages are Python‑2–only). On the existing Python 2 dev/CI setup pip install -r requirements.txt will now fail with “Django 4.2 requires Python >=3.8”, preventing the application from installing dependencies or running. Unless the entire stack is ported to Python 3 alongside this change, this upgrade is a build‑blocking regression.

Useful? React with 👍 / 👎.

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