Bump psycopg[binary] from 3.1.19 to 3.2.1

[dependabot]

Bumps psycopg[binary] from 3.1.19 to 3.2.1.

Changelog

Sourced from psycopg[binary]'s changelog.

.. currentmodule:: psycopg

.. index:: single: Release notes single: News

psycopg release notes

Future releases

Psycopg 3.2.2 (unreleased) ^^^^^^^^^^^^^^^^^^^^^^^^^^

• Drop !TypeDef specifications as string from public modules, as they cannot be composed by users as !typing objects previously could (:ticket:[#860](https://github.com/psycopg/psycopg/issues/860)).

Current release

Psycopg 3.2.1 ^^^^^^^^^^^^^

• Fix packaging metadata breaking [c], [binary] dependencies (:ticket:[#853](https://github.com/psycopg/psycopg/issues/853)).

Psycopg 3.2

.. rubric:: New top-level features

• Add support for integer, floating point, boolean NumPy scalar types__ (:ticket:[#332](https://github.com/psycopg/psycopg/issues/332)).
• Add !timeout and !stop_after parameters to Connection.notifies() (:ticket:340).
• Allow dumpers to return !None, to be converted to NULL (:ticket:[#377](https://github.com/psycopg/psycopg/issues/377)).
• Add :ref:raw-query-cursors to execute queries using placeholders in PostgreSQL format ($1, $2...) (:tickets:[#560](https://github.com/psycopg/psycopg/issues/560), [#839](https://github.com/psycopg/psycopg/issues/839)).
• Add capabilities object to :ref:inspect the libpq capabilities <capabilities> (:ticket:[#772](https://github.com/psycopg/psycopg/issues/772)).
• Add ~rows.scalar_row to return scalar values from a query (:ticket:[#723](https://github.com/psycopg/psycopg/issues/723)).
• Add ~Connection.cancel_safe() for encrypted and non-blocking cancellation when using libpq v17. Use such method internally to implement !KeyboardInterrupt and ~cursor.copy termination (:ticket:[#754](https://github.com/psycopg/psycopg/issues/754)).
• The !context parameter of sql objects ~sql.Composable.as_string() and ~sql.Composable.as_bytes() methods is now optional (:ticket:[#716](https://github.com/psycopg/psycopg/issues/716)).
• Add ~Connection.set_autocommit() on sync connections, and similar

... (truncated)

Commits

• bb47d39 chore: bump psycopg package version to 3.2.1
• 55490a2 fix: fix versions in packaging metadata
• 1cbc42a docs: fix title level of major releases
• 06a6e5e docs: mention dropping Python 3.7 in psycopg 3.2 release
• ea3735d docs: better organization of the 3.2 release notes
• 896eee2 chore: bump psycopg package version to 3.2.0
• 2e2f4d7 chore: bump psycopg package version to 3.1.20
• 7369d3b Merge pull request #846 from eli-schwartz/tomllib
• 6672c70 style: shorter line in pyproject.toml
• a517bb4 build: avoid installing tomli on recent python
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dryrunsecurity]

Hi there 👋, @DryRunSecurity here, below is a summary of our analysis and findings.

DryRun Security	Status	Findings
Server-Side Request Forgery Analyzer	✅	0 findings
Configured Codepaths Analyzer	✅	0 findings
IDOR Analyzer	✅	0 findings
Sensitive Files Analyzer	❕	1 finding
SQL Injection Analyzer	✅	0 findings
Authn/Authz Analyzer	✅	0 findings
Secrets Analyzer	✅	0 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 provided code change is an update to the requirements.txt file for the DefectDojo application, a web-based tool for managing the software vulnerability management lifecycle. The key change is an update to the psycopg[binary] package, a database adapter for the PostgreSQL database, from version 3.1.19 to version 3.2.1. This update likely includes bug fixes and improvements. From an application security perspective, the changes in this file do not directly impact the application's security, but it's important to review the changes to these dependencies for any potential security vulnerabilities or updates that could affect the application's security. The presence of critical security-related packages, such as cryptography, django-ratelimit, and argon2-cffi, suggests that the application has implemented various security features, which is a positive sign. Overall, the changes in this requirements.txt file appear to be routine updates and do not raise any immediate security concerns, but ongoing monitoring for known vulnerabilities in the dependencies is recommended.

Files Changed:

• requirements.txt: This file has been updated to include a newer version of the psycopg[binary] package, which is a database adapter for the PostgreSQL database. The update from version 3.1.19 to 3.2.1 likely includes bug fixes and improvements. The file also includes other security-related packages, such as cryptography, django-ratelimit, and argon2-cffi, which suggests the application has implemented various security features.

Powered by DryRun Security

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud

[mtesauro]

Approved