Skip to content

Dbtrail

v0.12.0 Breaking

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

Published 1mo 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

Summary

AI summary

Console now requires username+password login for first‑run browser setup.

Full changelog

Changelog

  • caa11bdf3b93cd0d2919e207ab8bf02a1111f45c Bump version to 0.12.0, update changelog
  • 3d9cafa8db42ae44562baf341cdc1fe124b67c43 docs(readme): document console password login and the persisted token
  • 05c2f47f4f46fe0a97cfabea5fe299290bf6295c feat(console): make username+password the only login path (first-run browser setup) (#454)
  • 0c43a47c1411063960a4ce8931015cfcb5b85c28 fix(console): pad the login/password overlay so its text isn't clipped (#452)
  • 82dbe78679794b74a9796547eec124f1d53c1cc3 fix(console): tighten the login/password dialog layout and message font (#453)

Breaking Changes

  • Removed all non‑username/password authentication methods from first‑run browser console setup; only username+password login is allowed.

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

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]