What dolthub/dolt shipped

This week in Dolt: branch --orphan for unrelated histories, rebase plans keep their commits through GC, merge works when both branches make the same pk change, fixed swapped merge-preview schemas, and stricter rebase branch permissions.

This week in Dolt: dolt branch --orphan creates a branch with an unrelated history holding the contents of a start point. Rebase plans now store commits as commit addresses so garbage collection keeps a paused rebase's commits reachable, and rebase state, pre-merge heads, savepoint roots and temporary tables are kept across GC. Merges now succeed when both branches applied the same primary key change, and dolt_preview_merge_conflicts no longer shows swapped or shifted schemas. Branch control requires permissions on the rebased branch for its working branch, and handles @-delimited revisions.

This week: fixes for server crashes, REPLACE panics, and fsck now checks working sets. Also included: binlog virtual generated columns, statistics lookup for branch-qualified databases, and shutdown stability. Released in 2.6.2.

This week we shipped fixes for several crashes and panics, including a server crash from keyless index lookups and a REPLACE panic on keyless tables with unique indexes. fsck now validates working sets and in-progress merge or rebase state. Full binlog row images now include virtual generated-column values for CDC consumers. Optimizer statistics lookup for branch-qualified databases was fixed, and shutdown handling for multiplexed gRPC requests was improved to avoid a WaitGroup misuse panic. These changes are available in release 2.6.2.

Dolt 2.6.0 is out with a corrected dolt_merge() for long-running branches. This week also brought git's ORT merge mechanism, remote removal clearing branch upstreams, and three-dot diff warnings for multiple merge bases.

Dolt 2.6.0 is released. It changes dolt_merge() so long-running branches with multiple merges are handled more correctly, and 2.5.0 made it possible to commit on more than one branch in the same SQL transaction. This week also landed git's ORT merge mechanism, cleared stale branch upstreams when a remote is removed, added a warning for three-dot diffs with several merge bases, fixed schema merge conflicts on mixed-case CHECK columns, and improved DOLT_LOG projection.

This week: atomic multi-branch commits with dolt_commit_all, dolt_merge_bases() and merge-base --all, a remotesrv path traversal fix, authenticated cluster role headers, NULL keys in index lookup joins, and history kept across same-key table recreates.

This week in Dolt: atomic multi-branch transactions and commits via dolt_commit_all and the dolt_multi_branch_commit setting, a new dolt_merge_bases() table function plus an --all flag on dolt merge-base, and a fix for path traversal in standalone remotesrv. Cluster role headers are now authenticated before transitions are applied, index lookup joins allow NULL in the constant lookup key, and diff accepts retagged primary keys so history survives a same-key table recreate. We also fixed merges silently keeping one definition when both branches add the same generated column with different expressions or storage modes, and SyncRoots now returns the source root read error instead of reporting success.

This week: fdatasync with a padded journal on Linux for faster writes, accelerated lookup joins with SQL row inputs, dolt version now times out and caches failed release checks, foreign keys referencing renamed indexes fixed, and dolt_blame identifiers quoted with the engine's sc

This week in Dolt: write performance improved by using fdatasync on Linux with a padded journal, lookup joins with SQL row inputs were accelerated with shared iteration and type-aware key conversion, and dolt version now uses a 3s HTTP timeout while caching failed release checks. Foreign keys referencing a renamed index are fixed by extending the index renaming logic to ALTER INDEX, nonlocal tables now return ErrTableAlreadyExists, dolt_blame view identifiers use the engine's schema formatter, and the NBS storage lock contract is documented. The git remote cache repository is initialized with the remote's object format.

Dolt 2.4.0 is out. We optimized dolt log to O(N), fixed upsert privilege checks, improved Git transfer performance with anchor refs, and made nonlocal table schema handling more flexible.

Dolt 2.4.0 is available. This release includes significant performance improvements: dolt log is now O(N) instead of O(N^2), Git operations preserve fetch anchors for incremental transfers, and NBS spooling eliminates redundant reads. We fixed upsert authorization to properly require UPDATE privileges and improved nonlocal table schema handling. Users can now configure Git remotes for disk/speed tradeoffs with new settings.

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.

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.