chore(release): v1.10.0 - pg_dump executor
Build and Push / release (push) Successful in 1s
Build and Push / build (push) Successful in 17s

Move the pg_dump_executor changelog entry from Unreleased into 1.10.0 and
bump pyproject.toml accordingly, so the executor added in a14f134 ships.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
This commit is contained in:
2026-10-19 19:06:43 +02:00
co-authored by Claude Sonnet 5
parent 67a6f9205b
commit 714f657bef
2 changed files with 4 additions and 2 deletions
+3 -1
View File
@@ -6,13 +6,15 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/).
## [Unreleased]
## [1.10.0] - 2026-10-19
### Added
- `pg_dump_executor`: dumps every postgres-shared database individually (`docker exec
postgres-shared pg_dump -Fc`, version-matched inside that container rather than through this
image's PG17 client), plus a globals-only dump of roles. Each archive is verified with
`pg_restore --list` before being promoted — a zero-TOC archive is treated as a failed dump,
not a kept one. One database failing does not stop the others; the run is still reported
CRITICAL and every failure is named. Not yet registered as a scheduled task (T-7).
CRITICAL and every failure is named (T-7).
## [1.9.0] - 2026-08-11
+1 -1
View File
@@ -1,6 +1,6 @@
[project]
name = "the-scheduler"
version = "1.9.0"
version = "1.10.0"
description = "System-wide maintenance orchestration - backups, doc mirroring, cleanup, task automation"
readme = "README.md"
requires-python = ">=3.12"