From 46161026145452ea6bd518e816dd87ccf46ecd32 Mon Sep 17 00:00:00 2001
From: Brandon Sanchez <brandon.sanchez@cockroachlabs.com>
Date: Wed, 29 Apr 2026 14:02:50 -0400
Subject: [PATCH 1/2] April MOLT release notes

---
 src/current/releases/molt.md | 17 ++++++++++++++++-
 1 file changed, 16 insertions(+), 1 deletion(-)

diff --git a/src/current/releases/molt.md b/src/current/releases/molt.md
index 138bdcee184..6b1b10126ea 100644
--- a/src/current/releases/molt.md
+++ b/src/current/releases/molt.md
@@ -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 silently 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.
+</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.
 </section>
 
 <section class="filter-content" markdown="1" data-scope="replicator">

From a0d715b77f58d71e3f53c538803973eeb04edff6 Mon Sep 17 00:00:00 2001
From: Brandon Sanchez <brandon.sanchez@cockroachlabs.com>
Date: Thu, 30 Apr 2026 12:04:59 -0400
Subject: [PATCH 2/2] removed the word silently

---
 src/current/releases/molt.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/current/releases/molt.md b/src/current/releases/molt.md
index 6b1b10126ea..9a73aa5142f 100644
--- a/src/current/releases/molt.md
+++ b/src/current/releases/molt.md
@@ -34,7 +34,7 @@ Cockroach Labs recommends using the latest available version of each tool. Refer
 <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 silently corrupted during replication to CockroachDB. Binary values are now correctly hex-encoded before transmission, preserving data integrity.
+- 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.
 </section>