Merged PRs
dolt
- 11150: fix(git-remote-cache): ensure remote cache compaction and pruning occurs via new
Teardownlifecycle method
Adds a newTeardownlifecycle method toChunkStore(plusDoltDBandDoltDatabaseProvider) for Git remotes.Teardowndrives the expensive end-of-process cleanup —git gcand deletion of per-sessionUUIDrefs — that previously fired implicitly insideCloseand was therefore lost when the provider-level cache was removed.
Closeremains the cheap, deferrable per-operation hook; for the shared Git remoteNomsBlockStoreit is suppressed by a thin shim so caller defers don't tear down the shared instance. Also readds a provider-layer cache (Git remotes only) so aDoltDBis opened once per remote URL per process and reused across operations. At engine shutdown, the provider callsTeardownonce, which drains both caches, runs the GC + ref cleanup, then force-closes each shared store. - 11148: Fix
dolt statusto reportAUTO_INCREMENTvalue changes
ALTER TABLE foo AUTO_CINREMENT = Nupdated the table butdolt statuscontinued to report "nothing to commit".HasChangesIgnoringColumnTagsnow comparesGetAutoIncrementValuebetween from and to tables.
Fix #11145
- 11147: dump-docs: emit a description: field in the generated cli.md frontmatter
The dolt docs site (dolthub/docs-2) now readsdescription:from each page's frontmatter — it powers the per-entry summary inllms.txt(the agent-readable docs index) and is wired up for OG/Twitter cards.
cli.mdis generated bydolt dump-docs, so anydescription:added by hand to the docs repo gets overwritten on the next regeneration. Baking it into the constant header so it survives every regen. - 11146: dolt status doesn't require both --use-db and --branch
There was a gap in testing for the status command when you specify only --use-db, but no --branch name. This resulted in getting the error "could not find current branch commit"
Fixes: #11137
Closed Issues
- 11145:
dolt statusdoes not surface anauto_incrementchange - 11137:
statusrequires both--use-dband--brancharguments - 11142: Error: The current API does not support the selected model gpt-5.5
Performance
| Read Tests | MySQL | Dolt | Multiple |
|---|---|---|---|
| covering_index_scan | 17.32 | 2.3 | 0.13 |
| groupby_scan | 142.39 | 132.49 | 0.93 |
| index_join | 3.49 | 1.93 | 0.55 |
| index_join_scan | 4.25 | 1.34 | 0.32 |
| index_scan | 350.33 | 211.6 | 0.6 |
| oltp_point_select | 0.2 | 0.26 | 1.3 |
| oltp_read_only | 3.82 | 5.09 | 1.33 |
| select_random_points | 0.37 | 0.55 | 1.49 |
| select_random_ranges | 0.39 | 0.64 | 1.64 |
| table_scan | 350.33 | 204.11 | 0.58 |
| types_table_scan | 759.88 | 458.96 | 0.6 |
| reads_mean_multiplier | 0.86 |
| Write Tests | MySQL | Dolt | Multiple |
|---|---|---|---|
| oltp_delete_insert | 8.43 | 6.32 | 0.75 |
| oltp_insert | 4.18 | 3.19 | 0.76 |
| oltp_read_write | 9.22 | 11.45 | 1.24 |
| oltp_update_index | 4.41 | 3.36 | 0.76 |
| oltp_update_non_index | 4.18 | 3.07 | 0.73 |
| oltp_write_only | 5.28 | 6.32 | 1.2 |
| types_delete_insert | 8.58 | 6.79 | 0.79 |
| writes_mean_multiplier | 0.89 |
| TPC-C TPS Tests | MySQL | Dolt | Multiple |
|---|---|---|---|
| tpcc-scale-factor-1 | 94.1 | 52.69 | 1.79 |
| tpcc_tps_multiplier | 1.79 |
| Overall Mean Multiple | 1.18 |
|---|