What dolthub/dolt shipped
Written by FoxPlug from public releases; not affiliated with Dolthub. An automatic summary of the public release, pull request and commit data of github.com/dolthub/dolt. Dolthub did not write it and does not use or endorse FoxPlug. Every line links to the public change it describes.
Get a weekly update like this for your product, free
Week of September 21, 2026
What shipped
- Release 2.3.5 adds wildcard table filters for binlog replication, supporting REPLICATE_WILD_DO_TABLE and REPLICATE_WILD_IGNORE_TABLE with MySQL wildcard matching and precedence handling. Release
- Dynamic merge conflict handling allows flexible row merge behavior with the ability to detect conflicts on matching values and create rows based on caller requirements. Pull request #11643
- DoltgreSQL now supports transaction lifecycle hooks that expose transaction start, end reason (commit or rollback), and savepoint interaction. Pull request #11920
- DoltgreSQL can now override the effective user in search path $user substitution. Pull request #11933
- DoltgreSQL can now provide branch-control principal for access control. Pull request #11921
- TIME type precision changes have been implemented. Pull request #11943
Why it matters
The release brings improved MySQL replication capabilities with wildcard filtering support. DoltgreSQL gains important transaction lifecycle visibility and user context management features. The dynamic merge conflict handling opens new use cases for flexible row merge behavior.
Changelog entry
- Support wildcard table filters for binlog replication with REPLICATE_WILD_DO_TABLE and REPLICATE_WILD_IGNORE_TABLE Release
- Add dynamic merge conflict handling for flexible row merge behavior Pull request #11643
- Add DoltgreSQL transaction lifecycle hooks for transaction start, end, and savepoint events Pull request #11920
- Allow DoltgreSQL to override effective user in search path $user substitution Pull request #11933
- Allow DoltgreSQL to provide branch-control principal Pull request #11921
- Implement TIME type precision changes Pull request #11943
Dolt 2.3.5 ships wildcard table filters for binlog replication, matching MySQL's REPLICATE_WILD_DO_TABLE and REPLICATE_WILD_IGNORE_TABLE behavior. DoltgreSQL gains transaction lifecycle hooks and search path user override support.
Dolt 2.3.5 is out with significant improvements for MySQL-to-Dolt binlog replication. Wildcard table filters now support REPLICATE_WILD_DO_TABLE and REPLICATE_WILD_IGNORE_TABLE with full MySQL wildcard matching and precedence handling. DoltgreSQL adds transaction lifecycle hooks for visibility into transaction start, commit/rollback, and savepoint operations, plus enhanced search path user handling for better access control integration.
Week of September 14, 2026
What shipped
- Released version 2.3.4 with fixes for journal writer race conditions and session-only checkout warnings in noninteractive SQL. Release
- Fixed garbage collection bug where reads could access chunks that were being collected by draining outstanding reads before GC installs its keeper. Pull request #11891
- Fixed generation ordering on reads to prevent missing chunks that are being moved from new to old generation during garbage collection. Pull request #11892
- Improved keeper sampling in the read path by moving it into beginRead and registering all unlocked reads from a single locked section. Pull request #11889
- Added support for wildcard table filters in binlog replication with REPLICATE_WILD_DO_TABLE and REPLICATE_WILD_IGNORE_TABLE. Pull request #11842
- Added JSON Lines output format for SQL queries with one JSON object per row. Pull request #11849
- Enabled Dolt executable comments in SQL scripts. Pull request #11851
- Changed boolean SQL results to print as 1 and 0 in text and CSV output to match MySQL behavior. Pull request #11854
- Added validation of destination branch names before pushing to remotes. Pull request #11852
- Added validation and sanity checks on index data when NomsBlockStore opens table files. Pull request #11773
Why it matters
This week focused on critical garbage collection fixes that prevent data loss during collection cycles, along with improvements to replication, SQL output formatting, and branch validation. Several regression tests were added to prevent future issues with merges, procedures, and CSV handling.
Changelog entry
- Version 2.3.4 released Release
- Fixed GC race where reads could access chunks being collected Pull request #11891
- Fixed generation ordering on reads during chunk moves in GC Pull request #11892
- Improved keeper sampling in read path for consistency Pull request #11889
- Fixed lost cancellation wakeup in waitForGC Pull request #11888
- Fixed cache population before incoming Purge requests Pull request #11887
- Fixed nil-ghostGen bugs in GenerationalNBS Pull request #11893
- Added REPLICATE_WILD_DO_TABLE and REPLICATE_WILD_IGNORE_TABLE support Pull request #11842
- Added JSON Lines output format for SQL queries Pull request #11849
- Enabled Dolt executable comments in SQL scripts Pull request #11851
- Boolean SQL results now print as 1 and 0 in text and CSV output Pull request #11854
- Show ON UPDATE CURRENT_TIMESTAMP in EXTRA column Pull request #11844
- Validate destination branch names before pushing Pull request #11852
- Added index data validation and sanity checks in NomsBlockStore Pull request #11773
- Bumped Bazel to 9.2.0 and updated module versions Pull request #11618
v2.3.4 shipped with GC fixes preventing chunk collection races, wildcard replication filters, JSON Lines output, and improved branch validation.
Dolt 2.3.4 is out with important garbage collection fixes that prevent reads from accessing chunks being collected, plus new capabilities: wildcard filters for binlog replication, JSON Lines SQL output format, and better branch name validation before pushing.