This release contains backwards incompatible changes:

• Servers running as remote replicas now pull divergent remote heads (e.g. those pushed with dolt push -f) by default. This setting is controlled by the server variable @@dolt_read_replica_force_pull. This variable previously had a default of 0, and now defaults to 1. To restore the previous behavior on remote replicas, run set @@persist.dolt_read_replica_force_pull = 0 and restart the server.
• Certain stored procedures have a different result schema. dolt_gc and dolt_backup previously returned 1 for success and 0 for failure, and this has been reversed. Additionally, dolt_backup, dolt_fetch, dolt_gc, and dolt_push have changed the name of the column in their result schema, from success to status.

Per Dolt’s versioning policy, this is a minor version bump because applications written for older versions of dolt may need changes to continue functioning the same.

Merged PRs

dolt

• 6654: Standardize stored procedure success output messages
  Standardizes stored procedures that report a success/failure message to print Status of 0 on success and Status of 1 on failure. Changes from the old output of printing Success of 1 on success and Success of 0 on failure.
• 6651: fixes log panic
  Fixes panic when calling log in non-dolt repo by adding missing return statement.
• 6647: fix formatting issue in status
  fixes missing line break in dolt status when up to date with remote
• 6635: Change default of replication pull to force
  Fixes #6627
  This change alters the default of @@dolt_read_replica_force_pull from 0 to 1. By default, read replicas will now always pull from the remote, even when the current head has diverged (such as in the case of a commit --amend or push -f to the remote).
  Also changes dolt pull to automatically perform merges on the remote tracking branch as needed -- previously we required that this be a fast-forward merge only, which means that you couldn't pull down a force-pushed commit without a lot of other commands and headache.
  Also fixes a bug where boolean values couldn't be persisted with on or off.

Closed Issues

• 6653: Parse unique parameters for MySQL's MERGE engine.
• 6627: Amending commits on a primary breaks remote based replication
• 6645: Support TABLE_CHECKSUM as an alias for CHECKSUM
• 6632: Parse SECONDARY_ENGINE parameter in queries
• 6642: Support MySQL TABLE statement.
• 6585: Support for JSON modification functions

Latency