Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
17 changes: 16 additions & 1 deletion src/current/releases/molt.md
Original file line number Diff line number Diff line change
Expand Up @@ -23,11 +23,26 @@ Cockroach Labs recommends using the latest available version of each tool. Refer
<button class="filter-button" data-scope="replicator"><code>replicator</code></button>
</div>

### April 30, 2026

<section class="filter-content" markdown="1" data-scope="molt">
`molt` 1.4.0 is [available](#installation):

- MOLT Verify now supports PostgreSQL declarative partitioned tables.
</section>

<section class="filter-content" markdown="1" data-scope="replicator">
`replicator` 1.3.3 is [available](#installation):

- Fixed a bug where MySQL `BLOB`, `BINARY`, `VARBINARY`, and `MEDIUMBLOB` columns containing non-UTF-8 binary data were corrupted during replication to CockroachDB. Binary values are now correctly hex-encoded before transmission, preserving data integrity.
- Replication from MySQL sources now correctly replicates `NULL` values in `ENUM` columns.
Comment thread
bsanchez-the-roach marked this conversation as resolved.
</section>

### March 26, 2026
<section class="filter-content" markdown="1" data-scope="molt">
`molt` 1.3.7 is [available](#installation):

- Fixed a bug in MOLT Fetch v1.3.3-v1.3.6 where a transient error when scanning rows from the source database could cause retried queries to resume from an incorrect position, resulting in rows missing from the target database. Migrations from PostgreSQL and CockroachDB databases may have been exposed to this issue. Fetch retry attempts are recorded in the MOLT Fetch logs, and MOLT Verify will have detected any data discrepancies introduced by this bug.
- Fixed a bug in MOLT Fetch v1.3.3-v1.3.6 where a transient error when scanning rows from the source database could cause retried queries to resume from an incorrect position, resulting in rows missing from the target database. Migrations from PostgreSQL and CockroachDB databases may have been exposed to this issue. Fetch retry attempts are recorded in the MOLT Fetch logs, and MOLT Verify will have detected any data discrepancies introduced by this bug.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i cannot see what has changed here? seems fine tho

</section>

<section class="filter-content" markdown="1" data-scope="replicator">
Expand Down
Loading