diff --git a/.changeset/tame-pandas-verify.md b/.changeset/tame-pandas-verify.md
deleted file mode 100644
index 571e08f..0000000
--- a/.changeset/tame-pandas-verify.md
+++ /dev/null
@@ -1,22 +0,0 @@
----
-'@stackmade/gtm-as-code': patch
----
-
-`gtm-code verify` and `gtm-code doctor`, implementing ROADMAP.md milestone 0.8.
-
-- `gtm-code verify [--days <n>]` queries the GA4 Data API for every declared event over the trailing
-  N days (default 28) and reports which ones were never received — the check `plan`/`drift` can't
-  give you, since config can match GTM/GA4 exactly while the site never actually fires an event. For
-  a received event it also checks whether each `dimension: true` parameter was ever recorded with a
-  value; parameters not registered as a custom dimension are reported as unverifiable rather than
-  silently skipped, since the Data API has no way to query an arbitrary event parameter.
-- `gtm-code doctor` checks config validity, credentials, GTM/GA4 API reachability, and GA4 Data API
-  quota headroom, explaining what's missing instead of `plan`/`apply` failing mid-run with a raw
-  Google error.
-
-Both are live-verified against a real GA4 property. `doctor`'s quota check reads a real
-`tokensPerDay` figure on a standard non-360 property, and it tells "API not enabled" apart from
-"permission denied", which Google reports under the same `PERMISSION_DENIED` status. One caveat
-`verify` now states in its own output: the Data API's dimension schema is eventually consistent, so
-a parameter can be reported as not registered for a few minutes after `apply` created its custom
-dimension.
diff --git a/CHANGELOG.md b/CHANGELOG.md
index 2f335ea..c3645c3 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -1,5 +1,28 @@
 # @stackmade/gtm-as-code
 
+## 0.8.4
+
+### Patch Changes
+
+- 9b75e49: `gtm-code verify` and `gtm-code doctor`, implementing ROADMAP.md milestone 0.8.
+
+  - `gtm-code verify [--days <n>]` queries the GA4 Data API for every declared event over the trailing
+    N days (default 28) and reports which ones were never received — the check `plan`/`drift` can't
+    give you, since config can match GTM/GA4 exactly while the site never actually fires an event. For
+    a received event it also checks whether each `dimension: true` parameter was ever recorded with a
+    value; parameters not registered as a custom dimension are reported as unverifiable rather than
+    silently skipped, since the Data API has no way to query an arbitrary event parameter.
+  - `gtm-code doctor` checks config validity, credentials, GTM/GA4 API reachability, and GA4 Data API
+    quota headroom, explaining what's missing instead of `plan`/`apply` failing mid-run with a raw
+    Google error.
+
+  Both are live-verified against a real GA4 property. `doctor`'s quota check reads a real
+  `tokensPerDay` figure on a standard non-360 property, and it tells "API not enabled" apart from
+  "permission denied", which Google reports under the same `PERMISSION_DENIED` status. One caveat
+  `verify` now states in its own output: the Data API's dimension schema is eventually consistent, so
+  a parameter can be reported as not registered for a few minutes after `apply` created its custom
+  dimension.
+
 ## 0.8.3
 
 ### Patch Changes
diff --git a/package.json b/package.json
index c7525be..ad6841b 100644
--- a/package.json
+++ b/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@stackmade/gtm-as-code",
-  "version": "0.8.3",
+  "version": "0.8.4",
   "description": "GTM & GA4 as code — define Google Tag Manager and Analytics 4 config in YAML, plan/apply like Terraform.",
   "license": "MIT",
   "type": "module",