mirror of
https://github.com/kevinveenbirkenbach/docker-volume-backup.git
synced 2026-08-02 13:02:41 +00:00
Release version 3.3.0
This commit is contained in:
14
CHANGELOG.md
14
CHANGELOG.md
@@ -1,5 +1,19 @@
|
|||||||
# Changelog
|
# Changelog
|
||||||
|
|
||||||
|
## [3.3.0] - 2026-08-02
|
||||||
|
|
||||||
|
- Backup: *--volumes-no-backup-required* excludes a volume by name.
|
||||||
|
*--images-no-backup-required* resolves through *volume_is_fully_ignored*,
|
||||||
|
which skips a volume only when every container using it is ignored — a
|
||||||
|
container holding a derived tree beside state that must be kept cannot
|
||||||
|
express the exclusion at all. A docker-in-docker data root is exactly that
|
||||||
|
shape, and excluding by image would drop all three of its volumes.
|
||||||
|
- Backup: the name check runs before *containers_using_volume*, so an excluded
|
||||||
|
volume costs no docker inspection and the decision does not depend on which
|
||||||
|
containers exist when the run starts.
|
||||||
|
- Tests: two volumes off one container, asserting the sibling survives — the
|
||||||
|
property the image lever cannot provide — as unit and end-to-end.
|
||||||
|
|
||||||
## [3.2.2] - 2026-07-31
|
## [3.2.2] - 2026-07-31
|
||||||
|
|
||||||
- Backup: the btrfs snapshot is carved inside its subject, as
|
- Backup: the btrfs snapshot is carved inside its subject, as
|
||||||
|
|||||||
@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
|
|||||||
|
|
||||||
[project]
|
[project]
|
||||||
name = "backup-docker-to-local"
|
name = "backup-docker-to-local"
|
||||||
version = "3.2.2"
|
version = "3.3.0"
|
||||||
description = "Backup Docker volumes to local with rsync and optional DB dumps."
|
description = "Backup Docker volumes to local with rsync and optional DB dumps."
|
||||||
readme = "README.md"
|
readme = "README.md"
|
||||||
requires-python = ">=3.9"
|
requires-python = ">=3.9"
|
||||||
|
|||||||
Reference in New Issue
Block a user