release v1.5.0
Backup executors report their own outcome to check_history. The grant that makes it functional — INSERT for scheduler_user on the sysmon database — was applied 2026-08-11, so this deploy is the step that closes the gap: the backup domain has had no writer since the file-age poll was retired. Co-Authored-By: Claude <noreply@anthropic.com>
This commit is contained in:
+8
-4
@@ -6,14 +6,16 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/).
|
|||||||
|
|
||||||
## [Unreleased]
|
## [Unreleased]
|
||||||
|
|
||||||
|
## [1.5.0] - 2026-08-11
|
||||||
|
|
||||||
### Added
|
### Added
|
||||||
- Backup executors report their own outcome to the homelab health record — one row in
|
- Backup executors report their own outcome to the homelab health record — one row in
|
||||||
`check_history` per run, success or failure. Replaces a monitor that inferred backup health
|
`check_history` per run, success or failure. Replaces a monitor that inferred backup health
|
||||||
from file age and could not tell a failed backup from one that had not run yet.
|
from file age and could not tell a failed backup from one that had not run yet.
|
||||||
|
|
||||||
### Notes
|
### Notes
|
||||||
- Requires `GRANT INSERT ON check_history TO scheduler_user` in the `sysmon` database. Without
|
- Requires `GRANT INSERT ON check_history TO scheduler_user` in the `sysmon` database, applied
|
||||||
it the report is refused, logged, and skipped; the backup itself is unaffected.
|
2026-08-11. Without it the report is refused, logged, and skipped; the backup itself is unaffected.
|
||||||
|
|
||||||
## [1.4.0] - 2026-08-08
|
## [1.4.0] - 2026-08-08
|
||||||
|
|
||||||
@@ -280,14 +282,16 @@ TOTAL 80% 🎯
|
|||||||
|
|
||||||
## [Unreleased]
|
## [Unreleased]
|
||||||
|
|
||||||
|
## [1.5.0] - 2026-08-11
|
||||||
|
|
||||||
### Added
|
### Added
|
||||||
- Backup executors report their own outcome to the homelab health record — one row in
|
- Backup executors report their own outcome to the homelab health record — one row in
|
||||||
`check_history` per run, success or failure. Replaces a monitor that inferred backup health
|
`check_history` per run, success or failure. Replaces a monitor that inferred backup health
|
||||||
from file age and could not tell a failed backup from one that had not run yet.
|
from file age and could not tell a failed backup from one that had not run yet.
|
||||||
|
|
||||||
### Notes
|
### Notes
|
||||||
- Requires `GRANT INSERT ON check_history TO scheduler_user` in the `sysmon` database. Without
|
- Requires `GRANT INSERT ON check_history TO scheduler_user` in the `sysmon` database, applied
|
||||||
it the report is refused, logged, and skipped; the backup itself is unaffected.
|
2026-08-11. Without it the report is refused, logged, and skipped; the backup itself is unaffected.
|
||||||
|
|
||||||
### Planned
|
### Planned
|
||||||
- Redis integration for distributed locking
|
- Redis integration for distributed locking
|
||||||
|
|||||||
+1
-1
@@ -1,6 +1,6 @@
|
|||||||
[project]
|
[project]
|
||||||
name = "the-scheduler"
|
name = "the-scheduler"
|
||||||
version = "1.4.0"
|
version = "1.5.0"
|
||||||
description = "System-wide maintenance orchestration - backups, doc mirroring, cleanup, task automation"
|
description = "System-wide maintenance orchestration - backups, doc mirroring, cleanup, task automation"
|
||||||
readme = "README.md"
|
readme = "README.md"
|
||||||
requires-python = ">=3.12"
|
requires-python = ">=3.12"
|
||||||
|
|||||||
Reference in New Issue
Block a user