Repository navigation
chore: version packages - #11
Merged
Merged
Conversation
danielmlr
added a commit
that referenced
this pull request
Sep 25, 2026
The release workflow publishes every public package whose version is missing from npm, with or without a changeset: the run after #11 listed "These packages will be published as they were not found in the registry". Merged public, content-freshness@0.1.0 would have been in the next publish plan, and as a package npm does not know yet it cannot use trusted publishing, so every later release run would fail on it. The release PR removes the flag and adds the first changeset. AGENTS.md says so for any package that follows.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@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_viewsandanalytics__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 themcp:tools:analyticsormcp:toolsscope.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.