From 754edc2874d24f4af1b5cbffb8637058d89c21ff Mon Sep 17 00:00:00 2001 From: Daniel Date: Sun, 27 Sep 2026 20:21:21 +0200 Subject: [PATCH] chore(analytics): display name, test against EmDash 0.40.1 and 0.41.0 The manifest gets "name": "Analytics", which plugin-cli writes into the registry profile; without it registry results and a registry install's Plugins list show the slug. The comment above the description said registry search ignores keywords; it matches them now. The gating compat job adds 0.40.1 and 0.41.0. --- .changeset/analytics-display-name.md | 7 +++++++ .github/workflows/compat-matrix.yml | 2 +- AGENTS.md | 2 +- packages/analytics/README.md | 4 ++-- packages/analytics/emdash-plugin.jsonc | 9 +++++++-- 5 files changed, 18 insertions(+), 6 deletions(-) create mode 100644 .changeset/analytics-display-name.md diff --git a/.changeset/analytics-display-name.md b/.changeset/analytics-display-name.md new file mode 100644 index 0000000..3605dbf --- /dev/null +++ b/.changeset/analytics-display-name.md @@ -0,0 +1,7 @@ +--- +"@eisbachcode/emdash-plugin-analytics": patch +--- + +Gives the plugin the display name **Analytics**, which registry search results and the Plugins list of a registry install show instead of the slug `analytics`. A plugin registered in `plugins: []` still appears as `analytics` in the Plugins list, because EmDash names it after the plugin ID. + +Also tested on EmDash 0.40.1 and 0.41.0; neither needed a change. diff --git a/.github/workflows/compat-matrix.yml b/.github/workflows/compat-matrix.yml index d3df035..ac474e6 100644 --- a/.github/workflows/compat-matrix.yml +++ b/.github/workflows/compat-matrix.yml @@ -41,7 +41,7 @@ jobs: cache: pnpm - run: pnpm install --frozen-lockfile - run: pnpm typecheck - - run: ./scripts/compat-matrix.sh 0.39.0 0.39.1 0.40.0 + - run: ./scripts/compat-matrix.sh 0.39.0 0.39.1 0.40.0 0.40.1 0.41.0 latest: name: current EmDash (informational) diff --git a/AGENTS.md b/AGENTS.md index 1131a8c..997ccb9 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -43,7 +43,7 @@ pnpm install pnpm typecheck pnpm test # emdash-plugin validate, then vitest, per package pnpm build -./scripts/compat-matrix.sh 0.39.0 0.39.1 0.40.0 # suites against other EmDash releases +./scripts/compat-matrix.sh 0.39.0 0.39.1 0.40.0 0.40.1 0.41.0 # suites against other EmDash releases ``` ## Releases diff --git a/packages/analytics/README.md b/packages/analytics/README.md index bff6444..1a322a1 100644 --- a/packages/analytics/README.md +++ b/packages/analytics/README.md @@ -9,7 +9,7 @@ entry that earned them rather than to a URL string. > **Status: early releases.** Cloudflare Web Analytics plus demo data: a > dashboard widget, an Analytics page with a setup check, a per-entry page, > an Analytics panel in the entry editor and four read-only MCP tools. -> Tested on EmDash 0.39 and 0.40. See "Not in this version". +> Tested on EmDash 0.39 to 0.41. See "Not in this version". The screenshots show demo data on a site made from EmDash's blog template. @@ -137,7 +137,7 @@ After an update that changes a tool, EmDash stops serving the tools until they are approved again, but the switch stays on. Turn it off and on. **Sandboxed installs only, for now.** A plugin registered in `plugins: []` -gets none of its MCP tools on EmDash 0.39 and 0.40: the plugin build keeps +gets none of its MCP tools on EmDash 0.39 to 0.41: the plugin build keeps the tool declarations out of the runtime module, and EmDash's in-process loader looks for them only there. Under `sandboxed: []` or installed from the registry, the tools work. This is an EmDash limitation, not a setting. diff --git a/packages/analytics/emdash-plugin.jsonc b/packages/analytics/emdash-plugin.jsonc index 49b36ff..dff7124 100644 --- a/packages/analytics/emdash-plugin.jsonc +++ b/packages/analytics/emdash-plugin.jsonc @@ -27,8 +27,13 @@ ] } }, - // Registry search indexes slug and description and has no keywords - // field, so every provider this plugin supports has to be named here. + + // Registry results, and the Plugins list of a registry install, show this; + // without it they show the slug. In-process installs always show the slug. + "name": "Analytics", + + // Registry search matches the description and the keywords, so every + // provider this plugin supports is named in both. "description": "Cloudflare Web Analytics on the EmDash dashboard and next to your content: visits, page views, top pages, referrers and countries, with per-entry performance mapped back to the entries that produced it.", "keywords": ["analytics", "cloudflare", "dashboard", "widget", "content"],