-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Feat(psql): Use psycopg3 #10348
Feat(psql): Use psycopg3 #10348
Conversation
Hi there 👋, @DryRunSecurity here, below is a summary of our analysis and findings.
Note 🟢 Risk threshold not exceeded. Change Summary (click to expand)The following is a summary of changes in this pull request made by me, your security buddy 🤖. Note that this summary is auto-generated and not meant to be a definitive list of security issues but rather a helpful summary from a security perspective. Summary: The code changes in this pull request are focused on updating the From an application security perspective, the changes are positive as they help maintain the security posture of the application by keeping dependencies up-to-date and addressing potential security vulnerabilities. The application security engineer should review the changes carefully to ensure that the updated dependencies do not introduce any new vulnerabilities or compatibility issues. Additionally, the presence of some outdated dependencies, such as Files Changed:
Powered by DryRun Security |
Moved out of draft as tests are passing now |
This pull request has conflicts, please resolve those before we can evaluate the pull request. |
Conflicts have been resolved. A maintainer will review the pull request shortly. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Approved
Django 4.2 introduced support for Psycopg 3
This PR is blocked by #9493