This release fixes issues for SREs watching stability and regressions.
✓ No known CVEs patched in this version
Topics
+2 more
Summary
AI summaryFixed Largest Files panel failure on ClickHouse 26.x and preserved database plugin metadata during full catalog rebuilds.
Changes in this release
| Type | Severity | Summary | CVE |
|---|---|---|---|
| Feature | Medium |
Auto‑heals database list after Rebuild Catalog (Full) for MySQL/PostgreSQL/MongoDB plugins. Auto‑heals database list after Rebuild Catalog (Full) for MySQL/PostgreSQL/MongoDB plugins. Source: llm_adapter@2026-05-27 Confidence: high |
— |
| Bugfix | Medium |
Fixes empty Largest Files panel in newer ClickHouse versions. Fixes empty Largest Files panel in newer ClickHouse versions. Source: llm_adapter@2026-05-27 Confidence: high |
— |
| Bugfix | Medium |
Prevents Rebuild Catalog (Full) from wiping MySQL/PostgreSQL/MongoDB plugin metadata. Prevents Rebuild Catalog (Full) from wiping MySQL/PostgreSQL/MongoDB plugin metadata. Source: llm_adapter@2026-05-27 Confidence: low |
— |
Full changelog
Fixes
-
Largest Files panel empty on newer ClickHouse (#286) — the comparison
status != 'X'against theFixedString(1)status column trips strict type-checking in ClickHouse 26.x, causing the query to fail silently while the rest of the archive detail page renders normally. Cast the literal totoFixedString('X', 1)and split the two ClickHouse queries into independent try/catch blocks so one failure can't shadow the other. -
Rebuild Catalog (Full) no longer wipes MySQL/PostgreSQL/MongoDB plugin metadata (#294) —
catalog_syncused to delete every archive row for the repo and re-insert from the borg listing, losing the agent-reporteddatabases_backed_upJSON in the process. Now updates existing rows in place, inserts only genuinely new archives, and deletes only archives that have actually been pruned upstream. -
Auto-heal database list from the catalog (#294) — after a successful Rebuild Catalog (Full), any archive whose
databases_backed_upisNULLgets its database list reconstructed by scanning the freshly-populated catalog for the plugin'sdump_dir. Works formysql_dump(top-level.sql{,.gz}files),pg_dump(same), andmongo_dump(subdirectories underdump_dir). Users who already lost their MySQL/PG/Mongo restore button can recover it by clicking Rebuild Catalog (Full) once.
Weekly OSS security release digest.
The CVE patches and breaking changes that affected production tools this week. One email, every Sunday.
No spam, unsubscribe anytime.
Share this release
Related context
Related tools
Beta — feedback welcome: [email protected]