Database Lab Engine v4.2.2 - Admin Token Change and Sync Reliability Fixes

Database Lab Engine v4.2.2 shipped on November 11, 2026. The most important change for operators is a security fix: admin routes now accept only the shared verificationToken, and personal tokens no longer grant admin access. This is a breaking change for any client that called /admin/* with a personal token. It is a regular release, not a prerelease.

The full release notes and downloads are on the GitHub release page. The release also lands dependency bumps that address several Go standard library and nginx advisories.

Admin routes tightened

/admin/* routes now verify the shared verificationToken only. Personal tokens, controlled by platform.enablePersonalTokens, keep working on all other routes. If your automation hits admin endpoints with a personal token, switch it to the shared token before upgrading. This closes a privilege gap where a user level token could do admin level work.

Sync and clone stability fixes

A few changes here that matter if you run physical mode or multi pool setups:

  • Physical mode: if Postgres on the sync instance stops responding for 30 seconds, the engine saves diagnostics and restarts the sync container. Before, it could snapshot stale data indefinitely.
  • A panic in a background goroutine no longer kills the whole engine. A clone caught mid-operation now gets a final status instead of staying in a transient one.
  • After a config reload, scheduled snapshots and logical refreshes update dataStateAt in /status again. In earlier versions it stayed frozen until a restart.
  • A config reload during a logical refresh on a multi pool instance no longer leaves the refreshed pool marked empty with snapshots hidden. Pool state is now guarded against concurrent reloads.

Clone creation and restore fixes

Creating a clone with "restricted": true no longer fails when a database name needs quoting, such as app.24, APP_24_12, or a name with spaces. Logical restore gained several fixes as well:

  • skipPolicies: true now works for explicit databases: entries, root level directory dumps, custom format files, and a single file dumpLocation.
  • Plain text SQL dumps are discovered automatically, and an explicit databases: {postgres: {}} entry no longer adds --create.
  • With backupName: LATEST, WAL-G errors such as missing credentials or unreachable storage are reported directly instead of a generic failure.
  • A failed clone upgrade keeps pg_upgrade output in upgrade/logs/pg_upgrade_output.d, which should make those failures easier to debug.

Visibility and security bumps

The UI now shows a Data lag row, for example 2 hours 3 minutes, in the Summary section of the snapshot, clone, and branch pages. Good indicator if you need to judge whether a snapshot is fresh enough to use.

Binary and image updates worth noting:

  • Binaries are built with Go 1.27, fixing CVE-2026-78667, CVE-2026-97031, CVE-2026-111943 and other standard library CVEs.
  • UI and Swagger UI images run on nginx 1.30.6, clearing 17 nginx advisories from 2026.
  • klauspost/compress is bumped to 1.18.7, OpenTelemetry modules to 1.45.0, and dompurify to 3.4.17.

The release notes also list internal e2e test suite improvements and a Trivy scan change on feature branches. Those do not affect runtime behavior.

Where to get it

← All updates