What bytebase/dbhub shipped
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
Week of October 5, 2026
What shipped
- Version 1.5.0 is released, including SSH agent authentication, SQL Server verify-full TLS, and config fixes. Release
- SSH tunnels can now authenticate through an SSH agent, so sources no longer need
ssh_passwordorssh_keywhen the key lives in an agent. Pull request #457 - PostgreSQL IAM connections now authenticate on demand through pg's async password callback instead of rotating pools every 14 minutes. Pull request #421
- Query_timeout now uses a server-side
query_timeouton MySQL and a single client-side fallback on PostgreSQL, MySQL, and MariaDB, replacing the previous per-connector behavior. Pull request #465 - Postgres now re-reads sslcert, sslkey, and sslrootcert per connection so rotated certificates take effect without restarting the process. Pull request #463
- Readonly mode on Postgres now denies set_config() with
is_local= false, closing the path that allowed session state changes on pooled connections. Pull request #464 - The SQL Server
max_rowsrow limiter no longer breaks DISTINCT, TOP (n), OFFSET, PERCENT, WITH TIES, or batches when splicing TOP n. Pull request #462 - SQLite batches now run multi-statement batches in source order instead of running all writes before any reads. Pull request #470
- A dbhub.toml change now reloads config per source instead of disconnecting and reconnecting every source. Pull request #461
- Integration suites no longer fail intermittently on container teardown timeouts in afterAll hooks. Pull request #466
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
- Release v1.5.0. Release
- Feat(ssh): support SSH agent authentication. Pull request #457
- Fix(ssh): address review findings on SSH agent support. Pull request #458
- Fix: authenticate PostgreSQL IAM connections on demand. Pull request #421
- Fix(timeout): server-side
query_timeouton MySQL and one client-side fallback for PostgreSQL, MySQL, and MariaDB. Pull request #465 - Fix(postgres): re-read sslcert, sslkey, and sslrootcert per connection so rotated certificates take effect. Pull request #463
- Fix(postgres): deny set_config() in readonly mode. Pull request #464
- Fix(sqlserver): repair
max_rowsTOP rewrite for DISTINCT, TOP (n), OFFSET, PERCENT, WITH TIES, and batches. Pull request #462 - Fix(sqlite): run multi-statement batches in source order. Pull request #470
- Fix: reload TOML config per source instead of reconnecting every source. Pull request #461
- Test: stop integration suites failing on container teardown timeout. Pull request #466
- Test: trim duplicated tests across unit and integration suites. Pull request #460
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.
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
- Released v1.4.0 with PostgreSQL client certificate authentication and SQL Server TLS improvements. Release
- PostgreSQL connections now support sslcert/sslkey client certificate authentication for servers requiring certificate-based auth. Pull request #441
- SQL Server connections now support verify-full TLS mode with certificate and hostname verification. Pull request #443
- PostgreSQL DSN parser now rejects sslrootcert and unknown sslmode values to catch configuration errors earlier. Pull request #442
- TOML configuration validation now rejects empty sslmode values before falling back to DSN values across PostgreSQL, MySQL, MariaDB, SQL Server, and Oracle. Pull request #451
- Documentation updated to point at the correct location for database connector interface definitions. Pull request #447
- Added glama.json to enable claiming the Glama project listing. Pull request #440
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
- Add sslcert/sslkey client certificate authentication support for PostgreSQL Pull request #441
- Add verify-full TLS mode support for SQL Server with certificate and hostname verification Pull request #443
- Reject sslrootcert and unknown sslmode values in PostgreSQL DSNs Pull request #442
- Reject empty TOML sslmode values before DSN fallback for PostgreSQL, MySQL, MariaDB, SQL Server, and Oracle Pull request #451
- Add glama.json for Glama listing claim support Pull request #440
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.
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
- V1.3.0 released with Oracle connector support, per-source PostgreSQL pool sizing, and fixes for
max_rowsapplication on comment-prefixed and CTE queries. Release - Oracle connector now includes
health_checksupport to monitor connection pool status. Pull request #435 - Oracle added to README and architecture documentation. Pull request #434
- Oracle connector implemented with Testcontainers integration tests using the freely redistributable gvenzl/oracle-free 23ai image. Pull request #433
- Fixed DSN redaction to prevent raw passwords from appearing in error messages and startup logs. Pull request #431
- PostgreSQL sources now support
pool_max_connectionsoption to configure per-source connection limits from 1 to 1000. Pull request #427 - V1.2.5 released with recoverable AWS IAM refresh failures. Release
- AWS IAM refresh failures no longer delete sources, allowing tools to retry on the next refresh tick. Pull request #425
- PostgreSQL and MariaDB connectors now attach error listeners to connection pools to prevent crashes from dropped idle connections. Pull request #423
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
- Feat: Oracle connector with Testcontainers integration Release
- Feat:
health_checksupport for Oracle sources Pull request #435 - Docs: Oracle added to README and architecture documentation Pull request #434
- Feat(postgres):
pool_max_connectionsoption for per-source configuration Pull request #427 - Fix: prevent raw DSN from appearing in error messages Pull request #431
- Fix: apply
max_rowslimit to comment-prefixed and CTE queries Pull request #429 - Fix: AWS IAM refresh failures now recoverable instead of removing sources Pull request #425
- Fix(postgres,mariadb): attach pool error listeners to prevent crashes Pull request #423
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.
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.