v0.1.2
Umami Compass 0.1.2 — Automatic client updates
This release makes stable client updates explicit and unifies the release pipeline so npm, the official MCP Registry, and GitHub Releases cannot silently drift to different versions.
Note
This is primarily a distribution and operations release. It does not expand the analytics tool surface.
Highlights
- Update documented stdio configurations to run
umami-compass@latestwith--prefer-online, allowing npm to check the stable channel whenever the MCP process starts. - Document stable, preview, and exact-version channels, including the MCP restart required to load a newly installed version.
- Publish npm, exact MCP Registry metadata, and the GitHub Release from one tag-triggered workflow.
- Verify immutable package version, npm release channel, Registry propagation, and release metadata before completion.
- Make the workflow retry-safe: already-published artifacts are accepted only when they match the tagged commit.
Upgrade
Use the stable channel:
npx --yes --prefer-online umami-compass@latestReproduce this exact version:
npx --yes umami-compass@0.1.2MCP processes do not hot-swap their executable. Restart the process or client after an upgrade.
Verification
- 55 automated tests, lint, typecheck, build, and packed-package smoke testing.
- Release metadata checked against the exact
v0.1.2tag. - npm and MCP Registry publication verified by the release workflow.