1.2.3
Fixed
- Critical:
MAX_BACKUPSwas only rejected when it was the literal0, so00and000passed validation. Both reachhead -n -Nin the pruning step as0, andhead -n -0emits every line rather than none — the complete list of snapshots was handed torm -rfafter every run. - Important:
exec.shfails fast on a missingTOKEN, an invalidMAX_BACKUPSor an unknownTIME_ZONE. With arestartpolicy in place an invalid value now produces a restart loop rather than an idle container. - Important: The daily sleep is backgrounded and waited on, so
INT/TERMfire immediately. A container stop used to hit the grace period and exit 137; it now exits 143 within a second. - Log retention is grouped by run date, so it matches snapshot retention for multi-entity setups.
Changed
COMPRESSIONis off for an empty value and forno,false,off,0(case-insensitive), on for anything else. Previously any non-empty value enabled compression, soCOMPRESSION=nocompressed.COMPRESSION=GZIPis unaffected.- Soft-failure markers are defined once and shared by the warning detection and the notification card; the shared set matches
repository not accessiblewithout the formerSkippingprefix.
Added
- The smoke test grew from 3 to 13 checks: config validation, retention,
COMPRESSIONhandling and SIGTERM behaviour, each confirmed to fail against a deliberately broken image.
Images
ghcr.io/wus-technik/github-backup-docker:1.2.3 — also published as :stable (linux/amd64, linux/arm/v7, linux/arm64).