8000 [Snyk] Security upgrade jinja2 from 2.11.3 to 3.1.5 by MaxMood96 · Pull Request #136 · MaxMood96/cas · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

[Snyk] Security upgrade jinja2 from 2.11.3 to 3.1.5 #136

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.

Sign up for GitHub

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

Jump to bottom
Closed
wants to merge 1 commit into from
Closed

[Snyk] Security upgrade jinja2 from 2.11.3 to 3.1.5 #136

wants to merge 1 commit into from

Conversation

MaxMood96
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):

  • etc/loadtests/locust/requirements.txt
⚠️ Warning 
equests 2.24.0 has requirement urllib3!=1.25.0,!=1.25.1,<1.26,>=1.21.1, but you have urllib3 1.26.5.
jinja2 3.1.5 has requirement MarkupSafe>=2.0, but you have MarkupSafe 1.1.1.

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:

🦉 Learn about vulnerability in an interactive lesson of Snyk Learn.

@stale Stale
Copy link
stale bot commented Jan 3, 2025

This patch has been automatically marked as stale because it has not had recent activity. It will be closed in a few days if no further activity occurs. Thank you for your contributions.

Please take a look at the build status and make sure all relevant checks are passing with a green checkmark. Most importantly, make sure there are adequate unit tests that cover all changes/lines or appropriate integration tests if you're change affects an external system, or proper browser-tests if your changes affects UI interactions. Make sure your tests do not affect test coverage in a negative way. If your pull request is targeted at a branch other than main or master, please make sure you have a parallel pull request that contains the same change-set. You can cherry-pick your changes from the existing branch to a new branch that targets master.

@stale stale bot added the Pending label Jan 3, 2025
@stale Stale
Copy link
stale bot commented Jan 5, 2025

This patch has been automatically closed because it has not had recent activity. If you wish to resume work, please re-open the pull request and continue as usual. Thank you for your contributions.

@stale stale bot closed this Jan 5, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
Pending
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@MaxMood96 @snyk-bot
0