diff --git a/_data/releases/2.4/2.4.0.CR1.yml b/_data/releases/2.4/2.4.0.CR1.yml
new file mode 100644
index 00000000000..3fe69784a8b
--- /dev/null
+++ b/_data/releases/2.4/2.4.0.CR1.yml
@@ -0,0 +1,5 @@
+date: 2023-09-22
+version: "2.4.0.CR1"
+stable: false
+summary: Parallelizez incremental snapshot for MongoDB; Spanner connector is more robust in hgh-rebalance environment; Vitess connector retries most of the errors by default; Support for PostgresSQL 16; Spanner connector supports GKE identities
+#announcement_url:
diff --git a/releases/2.4/release-notes.asciidoc b/releases/2.4/release-notes.asciidoc
index 94393cda427..440ef9afb70 100644
--- a/releases/2.4/release-notes.asciidoc
+++ b/releases/2.4/release-notes.asciidoc
@@ -15,6 +15,69 @@ Release numbers follow http://semver.org[Semantic Versioning].
 
 toc::[]
 
+[[release-2.4.0-cr1]]
+== *Release 2.4.0.CR1* _(September 22nd 2023)_
+
+See the https://issues.redhat.com/secure/ReleaseNote.jspa?projectId=12317320&version=12413673[complete list of issues].
+
+=== Kafka compatibility
+
+This release has been built against Kafka Connect 3.5.1 and has been tested with version 3.5.1 of the Kafka brokers.
+See the https://kafka.apache.org/documentation/#upgrade[Kafka documentation] for compatibility with other versions of Kafka brokers.
+
+
+=== Upgrading
+
+Before upgrading any connector, be sure to check the backward-incompatible changes that have been made since the release you were using.
+
+When you decide to upgrade one of these connectors to 2.4.0.CR1 from any earlier versions,
+first check the migration notes for the version you're using.
+Gracefully stop the running connector, remove the old plugin files, install the 2.4.0.CR1 plugin files, and restart the connector using the same configuration.
+Upon restart, the 2.4.0.CR1 connectors will continue where the previous connector left off.
+As one might expect, all change events previously written to Kafka by the old connector will not be modified.
+
+If you are using our container images, then please do not forget to pull them fresh from https://quay.io/organization/debezium[Quay.io].
+
+
+=== Breaking changes
+
+Vitess connector was retrying only a subset of errors by default.
+This behaviour is changed and only explicitly defined errors are not retried (https://issues.redhat.com/browse/DBZ-6944[DBZ-6944]).
+
+
+
+=== New features
+
+* Update mongodb incremental snapshot to allow multiple threads reading chunks https://issues.redhat.com/browse/DBZ-6518[DBZ-6518]
+* Support for GKE workload identities https://issues.redhat.com/browse/DBZ-6885[DBZ-6885]
+* Support for PostgreSQL 16 https://issues.redhat.com/browse/DBZ-6911[DBZ-6911]
+* Vitess connector should retry on not found errors https://issues.redhat.com/browse/DBZ-6939[DBZ-6939]
+
+
+=== Fixes
+
+* Ad-hoc blocking snaps trigger emits schema changes of all tables https://issues.redhat.com/browse/DBZ-6828[DBZ-6828]
+* When the start_scn corresponding to the existence of a transaction in V$TRANSACTION is 0, log mining starts from the oldest scn when the oracle connector is started for the first time https://issues.redhat.com/browse/DBZ-6869[DBZ-6869]
+* Ensure that the connector can handle rebalance events robustly https://issues.redhat.com/browse/DBZ-6870[DBZ-6870]
+* OpenLogReplicator confirmation can resend or omit events on restarts https://issues.redhat.com/browse/DBZ-6895[DBZ-6895]
+* ExtractNewRecordState's schema cache is not updated with arrival of the ddl change event https://issues.redhat.com/browse/DBZ-6901[DBZ-6901]
+* Misleading Debezium error message when RDI port is not specified in application.properties https://issues.redhat.com/browse/DBZ-6902[DBZ-6902]
+* Generting protobuf files to target/generated-sources breaks build https://issues.redhat.com/browse/DBZ-6903[DBZ-6903]
+* Clean log printout in Redis Debezium Sink https://issues.redhat.com/browse/DBZ-6908[DBZ-6908]
+* Values being omitted from list of JSON object https://issues.redhat.com/browse/DBZ-6910[DBZ-6910]
+* fix logger named https://issues.redhat.com/browse/DBZ-6935[DBZ-6935]
+* MySql connector get NPE when snapshot.mode is set to never and signal data collection configured https://issues.redhat.com/browse/DBZ-6937[DBZ-6937]
+* Sanity check / retry for redo logs does not work per Oracle RAC thread https://issues.redhat.com/browse/DBZ-6938[DBZ-6938]
+* Drop events has wrong table changes information https://issues.redhat.com/browse/DBZ-6945[DBZ-6945]
+* Remove spaces from Signal and Notification MBean's ObjectName https://issues.redhat.com/browse/DBZ-6957[DBZ-6957]
+
+
+=== Other changes
+
+* Migrate all examples from mongodb.hosts to mongodb.connection.string https://issues.redhat.com/browse/DBZ-6893[DBZ-6893]
+
+
+
 [[release-2.4.0-beta2]]
 == *Release 2.4.0.Beta2* _(September 13rd 2023)_