From 06b6273d84b551f1dc2bc4827a0afa5e5334b13c Mon Sep 17 00:00:00 2001
From: "github-actions[bot]"
 <41898282+github-actions[bot]@users.noreply.github.com>
Date: Fri, 25 Sep 2026 20:15:02 +0000
Subject: [PATCH] chore: version packages

---
 .changeset/analytics-mcp-tools.md |  9 ---------
 packages/analytics/CHANGELOG.md   | 11 +++++++++++
 packages/analytics/package.json   |  2 +-
 3 files changed, 12 insertions(+), 10 deletions(-)
 delete mode 100644 .changeset/analytics-mcp-tools.md
 create mode 100644 packages/analytics/CHANGELOG.md

diff --git a/.changeset/analytics-mcp-tools.md b/.changeset/analytics-mcp-tools.md
deleted file mode 100644
index 8d65bdd..0000000
--- a/.changeset/analytics-mcp-tools.md
+++ /dev/null
@@ -1,9 +0,0 @@
----
-"@eisbachcode/emdash-plugin-analytics": minor
----
-
-Adds four read-only MCP tools, so an AI agent connected to EmDash's MCP server can ask for the numbers: `analytics__top_entries`, `analytics__unviewed_entries`, `analytics__entry_views` and `analytics__site_totals`. They read what the plugin has stored, never call Cloudflare, and every answer says which UTC days it covers, where stored history starts and when the last sync ran.
-
-The tools stay off until an administrator turns on **Agent access** for the plugin under Plugins. A caller needs `plugins:read` (editor and above) and a token with the `mcp:tools:analytics` or `mcp:tools` scope.
-
-On EmDash 0.39 and 0.40 only sandboxed and registry installs get the tools. A plugin registered in `plugins: []` lists none; that is an EmDash limitation, and nothing else about the plugin changes there.
diff --git a/packages/analytics/CHANGELOG.md b/packages/analytics/CHANGELOG.md
new file mode 100644
index 0000000..884ed71
--- /dev/null
+++ b/packages/analytics/CHANGELOG.md
@@ -0,0 +1,11 @@
+# @eisbachcode/emdash-plugin-analytics
+
+## 0.2.0
+
+### Minor Changes
+
+- 4ff7bd9: Adds four read-only MCP tools, so an AI agent connected to EmDash's MCP server can ask for the numbers: `analytics__top_entries`, `analytics__unviewed_entries`, `analytics__entry_views` and `analytics__site_totals`. They read what the plugin has stored, never call Cloudflare, and every answer says which UTC days it covers, where stored history starts and when the last sync ran.
+  
+  The tools stay off until an administrator turns on **Agent access** for the plugin under Plugins. A caller needs `plugins:read` (editor and above) and a token with the `mcp:tools:analytics` or `mcp:tools` scope.
+  
+  On EmDash 0.39 and 0.40 only sandboxed and registry installs get the tools. A plugin registered in `plugins: []` lists none; that is an EmDash limitation, and nothing else about the plugin changes there.
diff --git a/packages/analytics/package.json b/packages/analytics/package.json
index cd5b2b7..329c53a 100644
--- a/packages/analytics/package.json
+++ b/packages/analytics/package.json
@@ -1,6 +1,6 @@
 {
 	"name": "@eisbachcode/emdash-plugin-analytics",
-	"version": "0.1.0",
+	"version": "0.2.0",
 	"description": "EmDash plugin: Cloudflare Web Analytics on the dashboard and next to your content.",
 	"keywords": [
 		"emdash",