From 25fe6feba700e9b67143610456d0157c3308c09b Mon Sep 17 00:00:00 2001
From: Matthew Rollinson <matt@rolley.io>
Date: Tue, 21 Apr 2026 09:42:49 +0100
Subject: [PATCH 1/2] docs: wrap vue code samples in <template> for correct
 rendering

---
 README.md                          | 18 ++++++++++--------
 docs/components/consent-manager.md |  6 ++++--
 docs/components/dialog-link.md     |  4 +++-
 docs/components/dialog-trigger.md  |  8 +++++---
 docs/components/widget.md          | 30 ++++++++++++++++--------------
 docs/guide/iframe-blocking.md      | 14 ++++++++------
 6 files changed, 46 insertions(+), 34 deletions(-)

diff --git a/README.md b/README.md
index 9fc462c..98ae6a4 100644
--- a/README.md
+++ b/README.md
@@ -55,14 +55,16 @@ export default defineNuxtConfig({
 This renders both the banner and preferences dialog. You can also use `<C15tBanner>` and `<C15tDialog>` separately, or customise them via named slots:
 
 ```vue
-<C15tConsentManager>
-  <template #banner="{ acceptAll, acceptNecessary, openPreferences }">
-    <!-- your custom banner -->
-  </template>
-  <template #dialog="{ displayedConsents, toggle, saveCustom, acceptAll, close }">
-    <!-- your custom dialog -->
-  </template>
-</C15tConsentManager>
+<template>
+  <C15tConsentManager>
+    <template #banner="{ acceptAll, acceptNecessary, openPreferences }">
+      <!-- your custom banner -->
+    </template>
+    <template #dialog="{ displayedConsents, toggle, saveCustom, acceptAll, close }">
+      <!-- your custom dialog -->
+    </template>
+  </C15tConsentManager>
+</template>
 ```
 
 4. Check consent anywhere
diff --git a/docs/components/consent-manager.md b/docs/components/consent-manager.md
index f2a9141..05e16f2 100644
--- a/docs/components/consent-manager.md
+++ b/docs/components/consent-manager.md
@@ -23,8 +23,10 @@ A convenience component that renders both the consent banner and preferences dia
 This is equivalent to:
 
 ```vue
-<C15tBanner />
-<C15tDialog />
+<template>
+  <C15tBanner />
+  <C15tDialog />
+</template>
 ```
 
 ### Custom UI via Named Slots
diff --git a/docs/components/dialog-link.md b/docs/components/dialog-link.md
index 1f9d3b9..728927e 100644
--- a/docs/components/dialog-link.md
+++ b/docs/components/dialog-link.md
@@ -21,7 +21,9 @@ Inline trigger that opens the consent preferences dialog. Use it in body copy, f
 Renders a `<button>` by default. Use `as-anchor` to render an `<a>` instead:
 
 ```vue
-<C15tDialogLink as-anchor>Cookie settings</C15tDialogLink>
+<template>
+  <C15tDialogLink as-anchor>Cookie settings</C15tDialogLink>
+</template>
 ```
 
 ## Props
diff --git a/docs/components/dialog-trigger.md b/docs/components/dialog-trigger.md
index 77e6bb5..1115ec0 100644
--- a/docs/components/dialog-trigger.md
+++ b/docs/components/dialog-trigger.md
@@ -37,9 +37,11 @@ Mount once, typically in your `app.vue` alongside `<C15tBanner>` and `<C15tDialo
 The default icon is a cookie-ish dotted circle. Override via the default slot:
 
 ```vue
-<C15tDialogTrigger>
-  <Icon name="i-heroicons-cog-6-tooth" />
-</C15tDialogTrigger>
+<template>
+  <C15tDialogTrigger>
+    <Icon name="i-heroicons-cog-6-tooth" />
+  </C15tDialogTrigger>
+</template>
 ```
 
 ## Dragging
diff --git a/docs/components/widget.md b/docs/components/widget.md
index 73c5e15..d0c8bc2 100644
--- a/docs/components/widget.md
+++ b/docs/components/widget.md
@@ -29,20 +29,22 @@ Inline consent manager. Renders the same per-category toggles as `<C15tDialog>`
 All state is exposed via the default slot, so you can render any layout:
 
 ```vue
-<C15tWidget v-slot="{ displayedConsents, consents, toggle, saveCustom, acceptAll, rejectAll }">
-  <div v-for="ct in displayedConsents" :key="ct.name">
-    <input
-      type="checkbox"
-      :checked="consents[ct.name]"
-      :disabled="ct.disabled"
-      @change="toggle(ct.name, $event.target.checked)"
-    >
-    {{ ct.name }}
-  </div>
-  <button @click="rejectAll">Reject</button>
-  <button @click="saveCustom">Save</button>
-  <button @click="acceptAll">Accept all</button>
-</C15tWidget>
+<template>
+  <C15tWidget v-slot="{ displayedConsents, consents, toggle, saveCustom, acceptAll, rejectAll }">
+    <div v-for="ct in displayedConsents" :key="ct.name">
+      <input
+        type="checkbox"
+        :checked="consents[ct.name]"
+        :disabled="ct.disabled"
+        @change="toggle(ct.name, $event.target.checked)"
+      >
+      {{ ct.name }}
+    </div>
+    <button @click="rejectAll">Reject</button>
+    <button @click="saveCustom">Save</button>
+    <button @click="acceptAll">Accept all</button>
+  </C15tWidget>
+</template>
 ```
 
 ## Slot props
diff --git a/docs/guide/iframe-blocking.md b/docs/guide/iframe-blocking.md
index 1b69484..126a628 100644
--- a/docs/guide/iframe-blocking.md
+++ b/docs/guide/iframe-blocking.md
@@ -30,14 +30,16 @@ See the [`<C15tIframe>` component reference](/components/iframe) for custom plac
 Use any configured consent category:
 
 ```vue
-<!-- Marketing: ads, social embeds, retargeting -->
-<C15tIframe category="marketing" src="..." />
+<template>
+  <!-- Marketing: ads, social embeds, retargeting -->
+  <C15tIframe category="marketing" src="..." />
 
-<!-- Measurement: analytics embeds -->
-<C15tIframe category="measurement" src="..." />
+  <!-- Measurement: analytics embeds -->
+  <C15tIframe category="measurement" src="..." />
 
-<!-- Functionality: maps, chat widgets -->
-<C15tIframe category="functionality" src="..." />
+  <!-- Functionality: maps, chat widgets -->
+  <C15tIframe category="functionality" src="..." />
+</template>
 ```
 
 ## Automatic blocking of raw `<iframe>` elements

From 3e5013a07e0bff0fa51df5432d602e177e9565be Mon Sep 17 00:00:00 2001
From: Matthew Rollinson <matt@rolley.io>
Date: Tue, 21 Apr 2026 09:42:58 +0100
Subject: [PATCH 2/2] chore(release): suppress changelogen's GitHub Release
 step
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

changelogen calls its own syncGithubRelease after pushing the tag. If
it can't authenticate (no GITHUB_TOKEN locally), it falls back to
opening the Release page in a browser — on every release.

The CI workflow already creates the GitHub Release via changelogithub
after publishing to npm, so the local side's attempt was redundant and
noisy. --no-github disables the entire local Release step.
---
 package.json | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/package.json b/package.json
index b52c47f..7a08d3e 100644
--- a/package.json
+++ b/package.json
@@ -30,8 +30,8 @@
     "dev": "npm run dev:prepare && nuxt dev playground",
     "dev:build": "nuxt build playground",
     "dev:prepare": "nuxt-module-build build --stub && nuxt-module-build prepare && nuxt prepare playground",
-    "release": "pnpm run lint && pnpm run test && pnpm run prepack && changelogen --release --push",
-    "release:next": "pnpm run lint && pnpm run test && pnpm run prepack && changelogen --release --prerelease --push",
+    "release": "pnpm run lint && pnpm run test && pnpm run prepack && changelogen --release --push --no-github",
+    "release:next": "pnpm run lint && pnpm run test && pnpm run prepack && changelogen --release --prerelease --push --no-github",
     "lint": "eslint .",
     "test": "vitest run",
     "test:watch": "vitest watch",