Skip to content
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.

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

[Snyk] Security upgrade werkzeug from 2.2.3 to 3.0.6 #1433

Closed
wants to merge 1 commit into from

Conversation

snarfed
Copy link
Owner

@snarfed snarfed commented Oct 28, 2024

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
⚠️ Warning
proto-plus 1.25.0 requires protobuf, which is not installed.
httplib2 0.22.0 requires pyparsing, which is not installed.
gunicorn 23.0.0 requires packaging, which is not installed.
grpc-google-iam-v1 0.13.1 requires grpcio, which is not installed.
grpc-google-iam-v1 0.13.1 requires protobuf, which is not installed.
googleapis-common-protos 1.65.0 requires protobuf, which is not installed.
google-cloud-tasks 2.17.0 requires protobuf, which is not installed.
google-cloud-ndb 2.3.2 requires protobuf, which is not installed.
google-cloud-ndb 2.3.2 requires redis, which is not installed.
google-cloud-logging 3.11.3 requires protobuf, which is not installed.
google-cloud-error-reporting 1.11.1 requires protobuf, which is not installed.
google-cloud-datastore 2.20.1 requires protobuf, which is not installed.
google-cloud-audit-log 0.3.0 requires protobuf, which is not installed.
google-cloud-appengine-logging 1.5.0 requires protobuf, which is not installed.
google-auth 2.15.0 requires pyasn1-modules, which is not installed.
google-api-core 2.19.1 requires protobuf, which is not installed.
flask-gae-static 1.0 requires pyyaml, which is not installed.
beautifulsoup4 4.12.3 requires soupsieve, which is not installed.

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:

🦉 Directory Traversal
🦉 Allocation of Resources Without Limits or Throttling

@snarfed
Copy link
Owner Author

snarfed commented Oct 28, 2024

Snyk, you keep complaining about vulnerabilities in old versions of libs when I'm already pinned to the new version that fixes them. Useless.

@snarfed snarfed closed this Oct 28, 2024
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