Shipped · Databases

What bytebase/dbhub shipped

The public repository of Dbhub · github.com/bytebase/dbhub

Written by FoxPlug from the repository's own releases; not affiliated with Dbhub. Paste your own repository in the box below and FoxPlug writes the same weekly update for your product. This page is an automatic summary of the releases, pull requests and commits in github.com/bytebase/dbhub; Dbhub did not write it and does not use or endorse FoxPlug. Every line links to the change it describes.

Get a weekly update like this for your product, free

Or Use it as a GitHub Action

See the update FoxPlug writes for dbhub, free

Week of November 2, 2026

What shipped

Why it matters

This week tightened several connection and safety edges: read-only execution on MySQL and MariaDB now actually blocks DDL, and unset environment variables in configuration fail fast instead of producing repeated failed logins. Oracle users get wallet and mutual TLS support that was previously out of reach, and result handling no longer silently drops duplicate columns.

Changelog entry

Example posts FoxPlug drafted from these changes. Not written or posted by the project.

Post for X

Dbhub v1.6.0 is out: Oracle now supports PEM wallets and server certificate DN for mTLS. Config rejects TOML sources with unset env vars, MySQL and MariaDB read-only runs now block DDL, and results keep repeated column names.

Post for LinkedIn

Dbhub v1.6.0 is out. The Oracle connector now supports PEM wallets and a server certificate DN for mutual TLS, so Autonomous Database instances that require it and private endpoints behind an internal name or IP can connect. Configuration now rejects TOML sources that reference unset environment variables, so a missing password fails at startup instead of producing repeated failed logins. On MySQL and MariaDB, read-only execution now stops DDL such as CREATE, DROP, ALTER, TRUNCATE and RENAME rather than letting it through. Per-source session settings are available for MySQL and PostgreSQL, and results with repeated column names now keep every column. DSN handling for bracketed IPv6 hosts was also fixed.

Week of October 5, 2026

What shipped

Why it matters

This week brings a new release plus fixes that touch how connections authenticate, time out, and pick up rotated certificates. People running long-lived servers or pooled connections should see fewer unexpected session state changes and fewer restarts to apply certificate or config updates. Test reliability and connector cleanup also reduce noise in CI.

Changelog entry

Example posts FoxPlug drafted from these changes. Not written or posted by the project.

Post for X

V1.5.0 is out. This week: SSH agent auth for tunnels, on-demand PostgreSQL IAM connections, per-connection cert re-reads, consistent query_timeout across connectors, readonly set_config denied, SQL Server max_rows fixes, and ordered SQLite batches.

Post for LinkedIn

Dbhub v1.5.0 is out. This week we shipped SSH agent authentication so sources can use keys held in an agent, and PostgreSQL IAM connections now authenticate on demand instead of rotating pools every 14 minutes. Certificates are re-read per connection so rotated sslcert, sslkey, and sslrootcert take effect without restarting. query_timeout now behaves consistently across PostgreSQL, MySQL, and MariaDB, readonly mode denies set_config, SQL Server max_rows no longer breaks valid T-SQL, SQLite batches run in source order, and TOML changes reload per source. Test suites were also trimmed and made less flaky.

Week of September 28, 2026

What shipped

Why it matters

This week brings stricter TLS configuration validation across multiple databases and adds certificate-based authentication for PostgreSQL, reducing silent configuration failures. Users connecting to secure PostgreSQL and SQL Server instances will have better control over certificate verification behavior.

Changelog entry

Example posts FoxPlug drafted from these changes. Not written or posted by the project.

Post for X

V1.4.0 released: PostgreSQL now supports client certificate authentication, SQL Server gets verify-full TLS mode, and configuration validation is stricter across all databases.

Post for LinkedIn

V1.4.0 is out. PostgreSQL connections now handle client certificate authentication for servers requiring it. SQL Server supports verify-full TLS with certificate and hostname verification. We also tightened validation to reject empty or invalid sslmode values in TOML and DSN configurations across PostgreSQL, MySQL, MariaDB, SQL Server, and Oracle.

Week of September 14, 2026

What shipped

Why it matters

Oracle support is now production-ready with health checks and integration tests. Recent fixes address critical stability issues with connection pool handling and credential exposure, while new configuration options let operators tune PostgreSQL performance per source.

Changelog entry

Example posts FoxPlug drafted from these changes. Not written or posted by the project.

Post for X

V1.3.0: Oracle connector with health_check support, PostgreSQL per-source pool sizing, DSN redaction fix, and max_rows applied to CTEs and comments.

Post for LinkedIn

V1.3.0 introduces Oracle database support with health monitoring and Testcontainers integration tests. PostgreSQL sources now allow per-source connection pool configuration. Security improvements prevent raw DSN exposure in errors. Stability fixes address connection pool error handling across PostgreSQL and MariaDB, and make AWS IAM refresh failures recoverable.

Weeks with too little public activity are left out rather than filled in. Last updated 2026-11-10.

Is this your repo? Ask us to remove this page.