diff --git a/.changeset/silly-actors-yell.md b/.changeset/silly-actors-yell.md
deleted file mode 100644
index e800c05..0000000
--- a/.changeset/silly-actors-yell.md
+++ /dev/null
@@ -1,8 +0,0 @@
----
-"@stackmade/gtm-as-code": minor
----
-
-Extend protected resources to GA4. `protected: true` on a `ga4.dimensions`/`metrics`/`keyEvents`
-entry now needs `--allow-destroy-protected` before `apply` deletes it, tracked in
-`.analytics/state.json` since GA4 has no field of its own to stamp the flag into (GTM resources
-already worked this way).
diff --git a/.changeset/thirty-plums-argue.md b/.changeset/thirty-plums-argue.md
deleted file mode 100644
index 2a3c903..0000000
--- a/.changeset/thirty-plums-argue.md
+++ /dev/null
@@ -1,14 +0,0 @@
----
-"@stackmade/gtm-as-code": minor
----
-
-Add consent settings, consent/PII validation, and protected resources.
-
-- `gtm.tags.*.consent` and `events.*.consent` map to GTM's per-tag `consentSettings`, and a bare
-  `consentInit` trigger type is now supported for firing a default-consent tag before everything
-  else.
-- Validation now fails when a `ga4Event`/`googleTag` tag, or an `events.*` entry (which compiles
-  to one), has no `consent` block, and when an event parameter name suggests personal data
-  (`email`, `phone`, `address`, and similar).
-- `protected: true` on a GTM resource requires `--allow-destroy-protected`, on top of
-  `--allow-destroy`, before `apply` deletes it. GA4 resources aren't covered yet.
diff --git a/CHANGELOG.md b/CHANGELOG.md
index 82700ea..9338d69 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -1,5 +1,24 @@
 # @stackmade/gtm-as-code
 
+## 0.5.0
+
+### Minor Changes
+
+- 052149c: Extend protected resources to GA4. `protected: true` on a `ga4.dimensions`/`metrics`/`keyEvents`
+  entry now needs `--allow-destroy-protected` before `apply` deletes it, tracked in
+  `.analytics/state.json` since GA4 has no field of its own to stamp the flag into (GTM resources
+  already worked this way).
+- 694b6b8: Add consent settings, consent/PII validation, and protected resources.
+
+  - `gtm.tags.*.consent` and `events.*.consent` map to GTM's per-tag `consentSettings`, and a bare
+    `consentInit` trigger type is now supported for firing a default-consent tag before everything
+    else.
+  - Validation now fails when a `ga4Event`/`googleTag` tag, or an `events.*` entry (which compiles
+    to one), has no `consent` block, and when an event parameter name suggests personal data
+    (`email`, `phone`, `address`, and similar).
+  - `protected: true` on a GTM resource requires `--allow-destroy-protected`, on top of
+    `--allow-destroy`, before `apply` deletes it. GA4 resources aren't covered yet.
+
 ## 0.4.0
 
 ### Minor Changes
diff --git a/package.json b/package.json
index 1fac0d7..13b93b6 100644
--- a/package.json
+++ b/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@stackmade/gtm-as-code",
-  "version": "0.4.0",
+  "version": "0.5.0",
   "description": "GTM & GA4 as code — define Google Tag Manager and Analytics 4 config in YAML, plan/apply like Terraform.",
   "license": "MIT",
   "type": "module",