diff --git a/.changeset/c3-frameworks-update-4125.md b/.changeset/c3-frameworks-update-4125.md
deleted file mode 100644
index 0a956f3767a9..000000000000
--- a/.changeset/c3-frameworks-update-4125.md
+++ /dev/null
@@ -1,5 +0,0 @@
----
-"create-cloudflare": patch
----
-
-C3: Bumped `create-qwik` from `1.2.12` to `1.2.13`
diff --git a/.changeset/serious-beans-hug.md b/.changeset/serious-beans-hug.md
deleted file mode 100644
index 25c772cf1873..000000000000
--- a/.changeset/serious-beans-hug.md
+++ /dev/null
@@ -1,18 +0,0 @@
----
-"wrangler": minor
----
-
-Support TailEvent messages in Tail sessions
-
-When tailing a tail worker, messages previously had a null event
-property. Following https://github.com/cloudflare/workerd/pull/1248,
-these events have a valid event, specifying which scripts produced
-events that caused your tail worker to run.
-
-As part of rolling this out, we're filtering out tail events in the
-internal tail infrastructure, so we control when these new messages are
-forward to tail sessions, and can merge this freely.
-
-One idiosyncracy to note, however, is that tail workers always report an
-"OK" status, even if they run out of memory or throw. That is being
-tracked and worked on separately.
diff --git a/packages/create-cloudflare/CHANGELOG.md b/packages/create-cloudflare/CHANGELOG.md
index 5506cc748b1e..eeebe999bd34 100644
--- a/packages/create-cloudflare/CHANGELOG.md
+++ b/packages/create-cloudflare/CHANGELOG.md
@@ -1,5 +1,11 @@
 # create-cloudflare
 
+## 2.4.1
+
+### Patch Changes
+
+- [#4125](https://github.com/cloudflare/workers-sdk/pull/4125) [`d0e8e380`](https://github.com/cloudflare/workers-sdk/commit/d0e8e38035b7d65f99834700426d95dd88d54085) Thanks [@dependabot](https://github.com/apps/dependabot)! - C3: Bumped `create-qwik` from `1.2.12` to `1.2.13`
+
 ## 2.4.0
 
 ### Minor Changes
diff --git a/packages/create-cloudflare/package.json b/packages/create-cloudflare/package.json
index c5f1ff872c66..ae3f3580b772 100644
--- a/packages/create-cloudflare/package.json
+++ b/packages/create-cloudflare/package.json
@@ -1,6 +1,6 @@
 {
 	"name": "create-cloudflare",
-	"version": "2.4.0",
+	"version": "2.4.1",
 	"description": "A CLI for creating and deploying new applications to Cloudflare.",
 	"keywords": [
 		"cloudflare",
diff --git a/packages/wrangler/CHANGELOG.md b/packages/wrangler/CHANGELOG.md
index caf886dd1840..35b7f7198708 100644
--- a/packages/wrangler/CHANGELOG.md
+++ b/packages/wrangler/CHANGELOG.md
@@ -1,5 +1,24 @@
 # wrangler
 
+## 3.12.0
+
+### Minor Changes
+
+- [#4071](https://github.com/cloudflare/workers-sdk/pull/4071) [`f880a009`](https://github.com/cloudflare/workers-sdk/commit/f880a009ad7c7ec26a85c51f577164522a307217) Thanks [@matthewdavidrodgers](https://github.com/matthewdavidrodgers)! - Support TailEvent messages in Tail sessions
+
+  When tailing a tail worker, messages previously had a null event
+  property. Following https://github.com/cloudflare/workerd/pull/1248,
+  these events have a valid event, specifying which scripts produced
+  events that caused your tail worker to run.
+
+  As part of rolling this out, we're filtering out tail events in the
+  internal tail infrastructure, so we control when these new messages are
+  forward to tail sessions, and can merge this freely.
+
+  One idiosyncracy to note, however, is that tail workers always report an
+  "OK" status, even if they run out of memory or throw. That is being
+  tracked and worked on separately.
+
 ## 3.11.0
 
 ### Minor Changes
diff --git a/packages/wrangler/package.json b/packages/wrangler/package.json
index d984440442cf..2b8bef261fda 100644
--- a/packages/wrangler/package.json
+++ b/packages/wrangler/package.json
@@ -1,6 +1,6 @@
 {
 	"name": "wrangler",
-	"version": "3.11.0",
+	"version": "3.12.0",
 	"description": "Command-line interface for all things Cloudflare Workers",
 	"keywords": [
 		"wrangler",