Bump django-dbbackup from 4.1.0 to 4.2.0

[dependabot]

Bumps django-dbbackup from 4.1.0 to 4.2.0.

Release notes

Sourced from django-dbbackup's releases.

4.2.0

• Default HOST to localhost for postgres databases.
• Add PostgreSQL Schema support
• Fix restore of database from S3 storage by reintroducing inputfile.seek(0) to utils.uncompress_file
• Add warning for filenames with slashes in them
• Fix bug where dbbackup management command would not respect settings.py:DBBACKUP_DATABASES
• Remove usage of deprecated 'get_storage_class' function in newer Django versions
• Add support for new STORAGES (Django 4.2+) setting under the 'dbbackup' alias

Changelog

Sourced from django-dbbackup's changelog.

4.2.0 (2024-08-22)

• Default HOST to localhost for postgres databases.
• Add PostgreSQL Schema support
• Fix restore of database from S3 storage by reintroducing inputfile.seek(0) to utils.uncompress_file
• Add warning for filenames with slashes in them
• Fix bug where dbbackup management command would not respect settings.py:DBBACKUP_DATABASES
• Remove usage of deprecated 'get_storage_class' function in newer Django versions
• Add support for new STORAGES (Django 4.2+) setting under the 'dbbackup' alias

Commits

• 85c216f Fix docs theme (#531)
• cdf5fe6 Add dbbackup to docs dependencies (#530)
• 2f8f2b4 Fix docs workflow (#529)
• f486d3b Fix release workflow (#528)
• 1360515 v4.2.0 (#527)
• 28a02c3 [pre-commit.ci] pre-commit autoupdate (#516)
• b0fdd24 Add check for filename template values (#484)
• 8e15220 fixes for Django 5.1, add support for new STORAGES setting (#524)
• 16ca67c By default assume HOST is localhost for postgres databases. (#521)
• 6187954 #517 Use filehandle.size in utils.handle_size (#518)
• 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]

DryRun Security Summary

The provided patch updates the django-dbbackup library from version 4.1.0 to version 4.2.0 in the requirements.txt file, which is a routine library update that does not raise any immediate security concerns and should be reviewed for potential security vulnerabilities and tested for regressions or unexpected behavior changes.

Expand for full summary

Summary:

The code change in the provided patch updates the django-dbbackup library from version 4.1.0 to version 4.2.0 in the requirements.txt file. From an application security perspective, this update is not particularly interesting, as the django-dbbackup library is used for database backups, which is a common and essential feature in web applications. The version update is likely to include bug fixes, performance improvements, or compatibility updates with newer versions of Django or other dependencies.

However, it's always a good practice to review the release notes or change log of any library updates to ensure there are no known security vulnerabilities that have been addressed. Additionally, it's recommended to thoroughly test the application after any library updates to ensure there are no regressions or unexpected behavior changes. Overall, this code change appears to be a routine library update and does not raise any immediate security concerns. The review of the application's security posture should continue by examining other parts of the codebase and dependencies.

Files Changed:

• requirements.txt: The django-dbbackup library has been updated from version 4.1.0 to version 4.2.0.

Code Analysis

We ran 9 analyzers against 1 file and 1 analyzer had findings. 8 analyzers had no findings.

Analyzer	Findings
Sensitive Files Analyzer	1 finding

Riskiness

🟢 Risk threshold not exceeded.

View PR in the DryRun Dashboard.

[dryrunsecurity]

DryRun Security Summary

The provided patch updates the django-dbbackup library from version 4.1.0 to version 4.2.0 in the requirements.txt file, which is a routine library update that does not raise any immediate security concerns, but it is recommended to review the release notes and thoroughly test the application to ensure there are no regressions or unexpected behavior changes.

Expand for full summary

Summary:

The code change in the provided patch updates the django-dbbackup library from version 4.1.0 to version 4.2.0 in the requirements.txt file. From an application security perspective, this update is not particularly interesting, as the django-dbbackup library is used for database backups, which is a common and essential feature in web applications. The version update is likely to include bug fixes, performance improvements, or compatibility updates with newer versions of Django or other dependencies.

However, it's always a good practice to review the release notes or change log of any library updates to ensure there are no known security vulnerabilities that have been addressed. Additionally, it's recommended to thoroughly test the application after any library updates to ensure there are no regressions or unexpected behavior changes. Overall, this code change appears to be a routine library update and does not raise any immediate security concerns. The review of the application's security posture should continue by examining other parts of the codebase and dependencies.

Files Changed:

• requirements.txt: The django-dbbackup library has been updated from version 4.1.0 to version 4.2.0.

Code Analysis

We ran 9 analyzers against 1 file and 1 analyzer had findings. 8 analyzers had no findings.

Analyzer	Findings
Sensitive Files Analyzer	1 finding

Riskiness

🟢 Risk threshold not exceeded.

View PR in the DryRun Dashboard.

[mtesauro]

@dependabot recreate

[dependabot]

Superseded by #10807.