Skip to content

Dbtrail

v0.7.2 Breaking

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

Published 2mo Relational Databases
✓ 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

Affected surfaces

auth breaking_upgrade

Summary

AI summary

Shim now defaults to strict mode with an opt‑in --allow-gaps flag.

Full changelog

Changelog

  • fde6830e010ec0a31a5706e8fa030451e54f1a5b Bump version to 0.7.2, update changelog
  • 1aa636919fda5cffd1f803393d784cfa954374de schema: clarify 002_drop_idx_file_pos.sql is operator-facing only (#252)
  • 5d0cfb7dafd664fab5866ac55d37f2f3cd20482c shim: default to strict mode; add --allow-gaps opt-in (#258)
  • b12aef15eaea827ebdac0dd89f96ed15f89b74ac shim: fix auth + wire ArchiveFetcher (closes #254 #255) (#256)

Breaking Changes

  • Shim defaults to strict mode; previous behavior required explicit flag.
View diff on GitHub

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

Share on X Share on Bluesky

Track Dbtrail

Get notified when new releases ship.

Sign up free

About Dbtrail

All releases →

Related context

Earlier breaking changes

  • v0.30.0 Hard‑fail the whole batch when a PK value would overflow pk_values in indexer component.

Beta — feedback welcome: [email protected]