This release adds 2 notable features for engineering teams evaluating rollout.
✓ No known CVEs patched in this version
Topics
+14 more
Summary
AI summaryUpdates dolt, Closed Issues, and Merged PRs across a mixed release.
Changes in this release
| Type | Severity | Summary | CVE |
|---|---|---|---|
| Feature | Low |
Set version string in initial server response to configurable value Set version string in initial server response to configurable value Source: llm_adapter@2026-06-09 Confidence: high |
— |
| Bugfix | Medium |
Fixes Doltgres JSONB use with dolt_patch() function Fixes Doltgres JSONB use with dolt_patch() function Source: llm_adapter@2026-06-09 Confidence: high |
— |
Full changelog
Merged PRs
dolt
- 11179: Set version string in initial server response
MySQL servers return a version string in the initial connection response. Some clients read this and expect certain versions of MySQL or MariaDB. We return8.0.31by default, since that corresponds with the MySQL version we advertise feature parity with.
Currently, we use the@@versionsystem variable as the source of truth for the version string, and this can be configued via a server config file. But we extract the config for the listener before we initialize system variables. Previously this meant that the version string on connection defaulted to the value specified in our vitess dependency, which was hardcoded to8.0.31.
This PR changes the behavior to extract a string from the config if it exists.
We need to use a client integration test for this, since the Go SQL driver ignores the version in the connection info and does not provide a way to view it. - 11153: Bug fix: Doltgres
JSONBuse withdolt_patch()
Fixes https://github.com/dolthub/doltgresql/issues/2732
Closed Issues
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
Beta — feedback welcome: [email protected]