Skip to content

[Snyk] Fix for 2 vulnerabilities - #9

Open
ryanmcmorrowsnyk wants to merge 1 commit into
mainfrom
snyk-fix-3c37f00e1227277103fe78bfcccb6f4c
Open

[Snyk] Fix for 2 vulnerabilities#9
ryanmcmorrowsnyk wants to merge 1 commit into
mainfrom
snyk-fix-3c37f00e1227277103fe78bfcccb6f4c

Conversation

@ryanmcmorrowsnyk

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.txt
⚠️ Warning
inflect 6.0.5 has requirement pydantic<2,>=1.9.1, but you have pydantic 1.8.2.
graphql-relay 3.1.0 has requirement typing-extensions<4,>=3.7; python_version < "3.8", but you have typing-extensions 4.7.1.
google-api-core 1.34.1 has requirement protobuf!=3.20.0,!=3.20.1,!=4.21.0,!=4.21.1,!=4.21.2,!=4.21.3,!=4.21.4,!=4.21.5,<4.0.0dev,>=3.19.5, but you have protobuf 4.24.4.

Breaking Change Risk

Merge Risk: High

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 Request Forgery (CSRF)
🦉 Directory Traversal

@ryanmcmorrowsnyk

Copy link
Copy Markdown
Owner Author

Merge Risk: High

This upgrade includes a major version update for authlib which contains significant breaking changes requiring developer action. The mako upgrade also includes breaking changes related to Python version support.

authlib@0.15.4 → authlib@1.6.11

Risk: HIGH

The upgrade to version 1.0.0 of authlib introduces several major breaking changes:

  • SQLAlchemy Integration Removed: The built-in integration with SQLAlchemy has been removed. Developers are now required to define their own database models.
  • JOSE API Refactor: The JOSE implementation (JWS, JWE, JWK, JWT) has been refactored with name changes (e.g., JWS is now JsonWebSignature). The underlying Key model has also been redesigned.
  • Python 2 Support Dropped: Support for Python 2 has been completely removed.
  • Flask Provider Configuration: For the Flask OAuth 2.0 provider, the deprecated OAUTH2_JWT_XXX configuration keys have been removed.

Recommendation: This is a significant upgrade that will require code modifications. Review the official changelog and your application's usage of the SQLAlchemy integration and JOSE APIs before merging.

Source: Authlib Changelog

mako@1.1.4 → mako@1.3.11

Risk: MEDIUM

This upgrade drops support for older Python versions.

  • Python Version Requirement: Mako version 1.3.0 and later require Python 3.8 or newer. Support for Python 2.7, 3.6, and 3.7 has been dropped since the starting version of this upgrade.

Recommendation: Ensure your production environment is running Python 3.8 or a more recent version.

Source: Mako Changelog

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

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