Skip to content

build(deps-dev): update django-dbbackup requirement from ~=5.3.0 to ~=5.4.0 - #681

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/pip/django-dbbackup-approx-eq-5.4.0
Open

dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/pip/django-dbbackup-approx-eq-5.4.0

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Nov 2, 2026

Copy link
Copy Markdown
Contributor

Updates the requirements on django-dbbackup to permit the latest version.

Release notes

Sourced from django-dbbackup's releases.

5.4.0

Added

  • PostgreSQL connectors now forward the sslmode, sslrootcert, sslcert, sslkey, passfile and service keys of the Django database OPTIONS setting to pg_dump, psql and pg_restore as their matching libpq environment variable, the same way Django forwards them to its own command line tools. Backups and restores now use the TLS and client certificate configuration of the ORM, including the PostGIS activation step.

Changed

  • A value set in the PostgreSQL OPTIONS setting now takes precedence over the same variable configured through ENV, DUMP_ENV or RESTORE_ENV, where the environment used to win.

Fixed

  • ADMIN_PASSWORD is now passed to the PostGIS activation step, it had no effect until now.
  • PgDumpBinaryConnector now applies RESTORE_ENV to pg_restore, which was receiving DUMP_ENV instead. DUMP_ENV no longer leaks into the restore phase, put in RESTORE_ENV the variables which were reaching pg_restore from it.
  • DBBACKUP_GPG_ALWAYS_TRUST setting is now respected instead of being enabled whenever DBBACKUP_GPG_RECIPIENT is set. Encrypting to a public key that GPG does not trust will now fail, as documented, unless the key is trusted or DBBACKUP_GPG_ALWAYS_TRUST = True is set.
  • Pass configured DBBACKUP_CONNECTORS settings when instantiating connector from backup metadata in dbrestore.
  • dbrestore no longer discards the DROP and PG_OPTIONS values configured in DBBACKUP_CONNECTORS. --no-drop and --pg-options still take precedence when passed.
  • Connector options holding a list or a dict (EXCLUDE, SCHEMAS, ENV, DUMP_ENV, RESTORE_ENV) are now copied per connector. dbbackup --exclude-tables used to append to the class default, silently excluding those tables from every other database of the same run and from connectors created afterwards.
Changelog

Sourced from django-dbbackup's changelog.

[5.4.0] - 2026-10-24

Added

  • PostgreSQL connectors now forward the sslmode, sslrootcert, sslcert, sslkey, passfile and service keys of the Django database OPTIONS setting to pg_dump, psql and pg_restore as their matching libpq environment variable, the same way Django forwards them to its own command line tools. Backups and restores now use the TLS and client certificate configuration of the ORM, including the PostGIS activation step.

Changed

  • A value set in the PostgreSQL OPTIONS setting now takes precedence over the same variable configured through ENV, DUMP_ENV or RESTORE_ENV, where the environment used to win.

Fixed

  • ADMIN_PASSWORD is now passed to the PostGIS activation step, it had no effect until now.
  • PgDumpBinaryConnector now applies RESTORE_ENV to pg_restore, which was receiving DUMP_ENV instead. DUMP_ENV no longer leaks into the restore phase, put in RESTORE_ENV the variables which were reaching pg_restore from it.
  • DBBACKUP_GPG_ALWAYS_TRUST setting is now respected instead of being enabled whenever DBBACKUP_GPG_RECIPIENT is set. Encrypting to a public key that GPG does not trust will now fail, as documented, unless the key is trusted or DBBACKUP_GPG_ALWAYS_TRUST = True is set.
  • Pass configured DBBACKUP_CONNECTORS settings when instantiating connector from backup metadata in dbrestore.
  • dbrestore no longer discards the DROP and PG_OPTIONS values configured in DBBACKUP_CONNECTORS. --no-drop and --pg-options still take precedence when passed.
  • Connector options holding a list or a dict (EXCLUDE, SCHEMAS, ENV, DUMP_ENV, RESTORE_ENV) are now copied per connector. dbbackup --exclude-tables used to append to the class default, silently excluding those tables from every other database of the same run and from connectors created afterwards.

[5.3.1] - 2026-09-10

Changed

  • PostgreSQL HOST that are Unix/Windows socket paths will now be automatically URI-encoded to uphold pg_restore command line requirements.

Fixed

  • --verbosity parameter now correctly outputs log messages to the console instead of suppressing all output regardless of verbosity level.

[5.3.0] - 2026-04-09

Fixed

  • Fix compression when using DjangoConnector.
  • Fix an issue with paramiko os.stat sizes were larger on the target compared to the source.
  • Fix issue with dbrestore not finding backups when location is set in storage options.

[5.2.0] - 2026-02-10

Added

  • Added support for custom metadata writing and validation during operations via DBBACKUP_BACKUP_METADATA_SETTER and DBBACKUP_RESTORE_METADATA_VALIDATOR settings.

[5.1.2] - 2026-01-14

Fixed

  • Fixed a bug where metadata files were not being removed during clean-up.

[5.1.1] - 2026-01-07

... (truncated)

Commits

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 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)

Updates the requirements on [django-dbbackup](https://github.com/Archmonger/django-dbbackup) to permit the latest version.
- [Release notes](https://github.com/Archmonger/django-dbbackup/releases)
- [Changelog](https://github.com/Archmonger/django-dbbackup/blob/master/CHANGELOG.md)
- [Commits](Archmonger/django-dbbackup@5.3.0...5.4.0)

---
updated-dependencies:
- dependency-name: django-dbbackup
  dependency-version: 5.4.0
  dependency-type: direct:development
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file python Pull requests that update Python code labels Nov 2, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file python Pull requests that update Python code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants