Skip to content

dolt

v2.1.2 Breaking

This release includes 1 breaking change for platform teams planning a safe upgrade.

Published 1d Relational Databases
✓ No known CVEs patched
Read the diff → Tool health → What is this tool? →

✓ No known CVEs patched in this version

Topics

agent-memory agent-memory-server ai-agents ai-database data-version-control data-versioning
+14 more
database database-version-control database-versioning decentralized-database git git-database git-for-data git-for-databases git-sql immutable-database mariadb mysql sql version-controlled-database

Summary

AI summary

Updates dolt, Verified, and Closed Issues across a mixed release.

Changes in this release

Feature Low

Emit a description field in generated `cli.md` frontmatter for dolt docs site

Emit a description field in generated `cli.md` frontmatter for dolt docs site

Source: llm_adapter@2026-06-03

Confidence: high

Bugfix Medium

Fix `dolt status` to report AUTO_INCREMENT value changes

Fix `dolt status` to report AUTO_INCREMENT value changes

Source: llm_adapter@2026-06-03

Confidence: high

Bugfix Medium

Allow `dolt status` without both --use-db and --branch flags

Allow `dolt status` without both --use-db and --branch flags

Source: llm_adapter@2026-06-03

Confidence: high

Refactor Low

Add `Teardown` lifecycle method to `ChunkStore`, `DoltDB`, and `DoltDatabaseProvider` for Git remote cache cleanup

Add `Teardown` lifecycle method to `ChunkStore`, `DoltDB`, and `DoltDatabaseProvider` for Git remote cache cleanup

Source: llm_adapter@2026-06-03

Confidence: high

Full changelog

Merged PRs

dolt

  • 11150: fix(git-remote-cache): ensure remote cache compaction and pruning occurs via new Teardown lifecycle method
    Adds a new Teardown lifecycle method to ChunkStore (plus DoltDB and DoltDatabaseProvider) for Git remotes. Teardown drives the expensive end-of-process cleanup — git gc and deletion of per-session UUID refs — that previously fired implicitly inside Close and was therefore lost when the provider-level cache was removed.
    Close remains the cheap, deferrable per-operation hook; for the shared Git remote NomsBlockStore it 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 a DoltDB is opened once per remote URL per process and reused across operations. At engine shutdown, the provider calls Teardown once, which drains both caches, runs the GC + ref cleanup, then force-closes each shared store.
  • 11148: Fix dolt status to report AUTO_INCREMENT value changes
    ALTER TABLE foo AUTO_CINREMENT = N updated the table but dolt status continued to report "nothing to commit".
    • HasChangesIgnoringColumnTags now compares GetAutoIncrementValue between from and to tables.
      Fix dolthub/dolt#11145
  • 11147: dump-docs: emit a description: field in the generated cli.md frontmatter
    The dolt docs site (dolthub/docs-2) now reads description: from each page's frontmatter — it powers the per-entry summary in llms.txt (the agent-readable docs index) and is wired up for OG/Twitter cards.
    cli.md is generated by dolt dump-docs, so any description: added by hand to the docs repo gets overwritten on the next regeneration. Baking it into the constant header so it survives every regen.
    The description string matches what dolthub/docs-2#103 has for site/dolt/src/content/reference/cli/cli.md, so a regen after this merges won't introduce any diff to cli.md beyond the usual command-output churn.

    Generated frontmatter

    ---
    title: CLI
    description: Full reference for the dolt command-line interface — every command, every flag, with examples.
    ---
    

    Verified

    • go build ./cmd/dolt clean.
    • Ran the built binary against /tmp/cli-test.md.
    • Substituted that file into the docs-2 tree and ran npm run build:dolt — clean.
    • The description carries through to the docs site's llms.txt entry for the CLI page.
  • 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: https://github.com/dolthub/dolt/issues/11137

Closed Issues

  • 11145: dolt status does not surface an auto_increment change
  • 11137: status requires both --use-db and --branch arguments
  • 11142: Error: The current API does not support the selected model gpt-5.5

Breaking Changes

  • Introduces a new `Teardown` lifecycle method in `ChunkStore`, `DoltDB`, and `DoltDatabaseProvider` for Git remote cache cleanup; existing code must invoke `Teardown` at process shutdown to avoid resource leaks.

Weekly OSS security release digest.

The CVE patches and breaking changes that affected production tools this week. One email, every Sunday.

No spam, unsubscribe anytime.

Share this release

Track dolt

Get notified when new releases ship.

Sign up free

About dolt

Dolt – Git for Data

All releases →

Related context

Earlier breaking changes

  • v2.0.4 `DOLT_CHECKOUT('<table>')` now gated with Write permission.

Beta — feedback welcome: [email protected]