Dbtrail

v0.47.0 Breaking

This release includes 1 breaking change for platform teams planning a safe upgrade.

Published 18h Relational Databases

View tool

✓ No known CVEs patched

Read the diff → Tool health → What is this tool? →

✓ No known CVEs patched in this version

Topics

binlog database dba-tools disaster-recovery mariadb mcp

+5 more

mysql percona-mysql point-in-time-recovery postgresql recovery

Summary

AI summary

Refuse full-table merges when baseline and events have mismatched keys.

Full changelog

Changelog

0c59b9c50f5e6946e04b70e6e43d993266ec2698 Bump version to 0.47.0, update changelog
c8339c462dfff58c1c9b6c4472159f185fe58f13 cascade: close the remaining silent-zero paths after the ON UPDATE work (#1147)
04b3c397627e6dc578df9c692dcc8cd16369a89c console: carry schema provenance in /api/schemas (#1071) (#1150)
9409a01287abeeea62cbc0a82c97f9b6050b86fe console: fall back to the process --baseline-dir/--baseline-s3 for registry servers without their own (#1010) (#1154)
c51bc5aa40756d2b206290116011ebb009616f92 console: honest search scope, keyboard a11y, rotation input validation (#1148)
2413a4ec3457f47b5083d173eb9686b6b42d315d env: raise scanner buffer to 1MiB and surface Scanner errors in env-file loader (#1145)
1b1b3a6a05c5316ce2b0b3f7c5e9d8c34cf845b6 ext: harden the audit seam — panic-safe Record, uncancelable emission contexts, honest session attribution (#1149)
25eddae8af811b32004633a81b89630f489046b1 reconstruct/verify: support binary-family primary keys against the baseline (#1156)
76fdfc163dadefe8f11bfe6ae6c78c13383eaf8c reconstruct: refuse a full-table merge whose baseline and events are keyed apart (#1161)
b4030d0543067fc6d8fa44275346d8780f80cbeb rotate/archive: content-derived pruning so backfilled events archived under the wrong hour label stay time-queryable (#1153)
6bfaac921987d755dd47747bb9e1bfdf62ad1917 status: make sustained event skipping visible via a Capture health verdict (#1152)
a40f13c4b06cf11485e8ba262a8c0e8591060641 verify: honest verdicts for legacy and young indexes in --check recover (#1151)