This release contains backwards incompatible changes:

• Dolt commands which have been migrated to use SQL (sql, add, blame, status, commit, branch) have new behavior which may impact existing user workflows. Specifically, If the --user flag is in use, there is a new --password argument which will be required. If one is not presented, you will be prompted for a password, and this will hang waiting for input. Furthermore, previously these commands would allow users to specify incorrect credentials silently. If bad credentials are given now, the commands will fail appropriately. If you want to use a password in your automated jobs, but don't want to specify the password on the command line, you can set the DOLT_CLI_PASSWORD environment variable.

Per Dolt’s versioning policy, this is a minor version bump (major.minor.patch).

Merged PRs

dolt

• 6237: chore: fmt modify
  unnecessary use of fmt.Sprintf
  use fmt.Errorf(...) instead of errors.New(fmt.Sprintf(...))
  use fmt.Printf instead of fmt.Println(fmt.Sprintf(...)) (but don't forget the newline)
• 6235: Bring back pretty content for commit when commiting to a local db
  The output of the commit command changed with: #6138
  This change brings back the pretty log command output when running in a local context. This is a temporary change since we probably won't get to the log command for awhile yet.
• 6234, 6233, 6232: Continuous Integration Updates
• 6229: Support for dolt_ procedures inside user stored procedures
  These are just tests, the actual necessary changes are in dolthub/go-mysql-server#1852
  This addresses a large part of #5829, but see the last comment there: because of how we analyze / execute stored procedures, things dolt_checkout() doesn't work in stored procedures in some cases (namely when using unqualified table names).
• 6176: Enable authentication in the CLI commands migrated to sql backend
  Enable Authentication in the following ways:
  • New Global Flag --password
  • DOLT_CLI_PASSWORD environment variable
  • Ask for a password with a prompt.
  • Automatic authentication to a server using the secret in the sql-server.lock file
    One significant change in behavior is that previously if a user presented a non-sense username/password, we'd accept it as a super user identity. If a real user was specified, we would promote that user to a super user - regardless of if the password was correct.
    Now, if a --user flag is presented, the user must present a password by flag, env var or prompt. If the user/pwd combination is not a known user, the command will fail. This applies to both local and remote mode.
    Important to call out that this isn't about security. If you want to be a super user, you can just not provide a --user. This behavior is to enable consistent behavior of client applications where they need to test permissions. We were making this impossible before because bad credentials were being promoted.
    Related: #3922

go-mysql-server

• 1848: IntDiv.Type() should always return either uint64 or int64
  Previously, our IntDiv.convertLeftRight() used IntDiv.Type() to determine the larger type between IntDiv.Left.Type() and IntDiv.Right.Type() to avoid precision loss when doing internal calculations. Now, that logic is moved from IntDiv.Type() to IntDiv.convertLeftRight(), and IntDiv.Type() can only return uint64 or int64.
  This should fix the sql correctness regression from dolthub/go-mysql-server#1834
• 1847: Fix TargetSchema.Resolved() to check targetSchema column default expressions
  A couple SchemaTarget implementations weren't checking if the targetSchema was resolved as part of the Resolved() method. Added tests, audited the other implementations, and simplified the logic to use a new method on Schema to check that column default expressions are resolved.
  Fixes: #6206
  Dolt CI Run: #6213
• 1839: Slow degenerate semi join, hoist select opt
  This enables recursive subquery decorrelations, and adds a hash join execution option for semi joins that is equivalent to cached subquery existence checks.

Closed Issues

• 5829: dolt_commit() will break some following statements in stored procedures

Latency