v0.1.2 — Registry publication fix

This patch release completes npm and official MCP Registry publication.

Fixed:

• case-sensitive MCP Registry ownership metadata now matches the canonical ObsidianCorps GitHub organization
• release workflow supports safe manual retries and skips npm versions that are already public

Verified before release:

• 56 automated tests across Node.js 20, 22, and 24
• lint, formatting, type checks, and production build
• live MCP Registry manifest validation
• clean-cache npx MCP handshake with all 17 tools discovered

v0.1.1 — npm launch fix

This patch release fixes CLI startup when the npm-installed executable is launched through its .bin symlink.

Verified before release:

• 55 automated tests across Node.js 20, 22, and 24
• lint, formatting, type checks, and production build
• official MCP Registry manifest validation
• clean-cache npx MCP handshake with all 17 tools discovered

The release workflow can now safely skip an already-published npm version during retries.

v0.1.0 — Initial release

First public release of ObsidianCorps Umami MCP.

• 17 read-only analytics workflows covering Umami v3.3.1
• Opt-in write and separately gated destructive tools
• Umami Cloud and self-hosted authentication, including automatic TOTP
• Stdio and Streamable HTTP transports
• Revenue, funnels, journeys, retention, replays, heatmaps, and Web Vitals
• Multi-architecture container image with provenance and SBOM

We are looking for early Umami users to test the server with their preferred MCP client and share feedback.