Bump kamal-backup from 0.4.0 to 0.4.1

[dependabot]

Bumps kamal-backup from 0.4.0 to 0.4.1.

Release notes

Sourced from kamal-backup's releases.

v0.4.1

Highlights

• Failed database dumps no longer leave valid-looking partial snapshots. PostgreSQL and MySQL dumps now run through Restic using --stdin-from-command, so a snapshot is committed only when the dump command succeeds. Scheduler messages also use explicit INFO and ERROR levels, making failures easier to alert on. Fixes #14 via #16.

• Docker-mounted directories can be restored safely. Production restores now replace the contents of a mounted directory without trying to replace the mount point itself. Files are restored before databases, preventing partial restores and preserving SQLite databases stored alongside file-backed data. Fixes #15 via #16, incorporating #12.

• Database-only backups now restore and drill correctly. Configurations without file paths skip the file-restore phase instead of failing because no type:files snapshot exists. Implemented in #10 and incorporated into #16.

Maintenance

• Updated the documentation dependency on concurrent-ruby in #17.
• Updated the json dependency in #18.

Contributors

• Francesco Kirchhoff (@​FrancescoK) contributed the SQLite-safe restore ordering in #12.
• Andrey Samsonov (@​kryzhovnik) contributed database-only restore and drill support in #10.
• Alexis Vernier (@​alxvernier) reported the partial database snapshot and logging problem in #14.
• Alexandr Stets (@​sanzstez) reported the Docker-mounted restore problem in #15.
• Carmine Paolino (@​crmne) integrated and hardened the fixes in #16 and completed the dependency updates in #17 and #18.

Full changelog: v0.4.0...v0.4.1

Commits

• 2d240d1 Release 0.4.1
• 595d2b9 Update json dependency (#18)
• a3eced8 Update concurrent-ruby in docs (#17)
• 5bd0bb7 Harden backup and restore integrity (#16)
• See full diff 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 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)

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.