Changelog

[1.8.1] - 2026-07-12

Restore: the postgres empty mode also drops user-owned collations in public; dumps containing CREATE COLLATION (e.g. OpenProject's ICU collation versions_name) no longer abort the replay with 'collation already exists'.
Maintenance: base image bumped from python 3.11-slim to 3.14-slim.

Swarm-aware backups and replayable restores.

Backup: swarm task containers are never stopped or started manually anymore; they are skipped visibly and backed up hot, while the sql dump stays the consistent database backup.
Backup: a container that vanishes between listing and inspect no longer aborts the run; a failing inspect on a container that still exists keeps failing loudly.
Backup: pg_dump runs with the no-owner and no-privileges flags so dumps are replayable by the owning app user.
Restore: the mariadb empty mode drops all tables in one client session with FOREIGN_KEY_CHECKS disabled; FK-linked parent tables no longer abort the replay with ERROR 1451.
Restore: the postgres empty mode drops only current-user-owned objects, and the replay skips superuser-only dump lines without ever touching COPY data blocks.
Restore: the replay streams the dump through a temp file instead of buffering it in memory; multi-GB dumps no longer OOM the restore.
Tooling: the e2e runner reaches the DinD daemon via docker exec instead of a host-published unencrypted API port.
Tooling: new end-to-end test reproducing the swarm stop flake, plus unit tests for the restore filters and the swarm probes; the suite is 36 unit, 9 integration and 30 e2e tests.
Tooling: Dependabot with auto-merge for minor and patch updates.

🔌 MariaDB SQL backups now connect over TCP loopback so the dump always matches the same wildcard-host grant the application uses — no more surprise ERROR 1045 Access denied when a localhost-bound auth row preempts.
🧪 New regression and bug-repro tests pin the TCP behaviour and prove it under the exact preemption setup that caused the production failure on MariaDB 12.
🩺 E2E test infrastructure: DinD bridge and inner daemon now default to MTU 1280 so registry pulls survive host paths with broken PMTUD (override via E2E_DIND_MTU).

🚀 Backup jobs now support all valid Docker Compose file names – case-insensitive and hassle-free.

Compose handling is now fully delegated to the Infinito.Nexus compose wrapper or plain docker compose, removing all custom env and file detection to ensure a single, consistent source of truth.

- Make databases.csv optional: missing or empty files now emit warnings and no longer break backups
Fix Docker CLI compatibility by switching to docker-ce-cli and required build tools

Baudolo now restarts Docker Compose stacks in a wrapper-aware way (with a docker compose fallback), ensuring that all Compose overrides and env files are applied identically to the Infinito.Nexus workflow.

- Introduced --dump-only-sql mode for reliable, SQL-only database backups (replaces --dump-only).
Database configuration in databases.csv is now strict and explicit (* or concrete database name only).
PostgreSQL cluster backups are supported via *.
SQL dumps are written atomically to avoid corrupted or empty files.
Backups are smarter and faster: ignored volumes are skipped early, file backups run only when needed.
Improved reliability through expanded end-to-end tests and safer defaults.

- Backup: In --dump-only-sql mode, fall back to file backups with a warning when no database dump can be produced (e.g. missing databases.csv entry).

- Backup: Log a warning and skip database dumps when no databases.csv entry is present instead of raising an exception; introduce module-level logging and apply formatting cleanups across backup/restore code and tests.
CLI: Switch to an FHS-compliant default backup directory (/var/lib/backup) and use a stable default repository name instead of dynamic detection.
Maintenance: Update mirror configuration and ignore generated .egg-info files.