Skip to content

v0.4.0

Choose a tag to compare

View all tags
@github-actions github-actions released this 16 Jul 07:57
v0.4.0
8ef2fc9
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Umami Compass 0.4.0 — Release impact you can trust

Umami Compass 0.4.0 makes release analysis more honest and actionable: insufficient performance data now leads the verdict, traffic loss is separated from lower browsing depth, overlapping deployments are treated as confounders, and every low-data result explains when and how to recheck.

Important

analyze_release_impact now returns a compact executive summary by default. Use detailLevel: "full" when you need complete traffic breakdowns, traffic-quality evidence, and per-metric Core Web Vital changes. The tool surface and read-only security model are unchanged.

Highlights

Insufficient data comes first

  • Return insufficient_data as the primary verdict when Core Web Vital samples do not meet the confidence threshold.
  • Report the exact post-release and baseline sample deficits instead of only marking individual metrics inconclusive.
  • Estimate recheckAt and a longer equal-window recommendation from the observed sample rate when a reliable estimate is possible.
  • Avoid inventing a recheck date when the observed sample rate is zero or the required window would exceed the supported limit.

Better traffic interpretation

  • Use visitors and visits to describe audience traffic instead of treating pageviews alone as traffic volume.
  • Report pageviews per visit separately as browsing-depth evidence.
  • Distinguish audience growth or decline from reduced or increased page depth and mixed audience signals.
  • Treat zero baselines and weak audience samples as insufficient evidence rather than assigning a confident direction.

Competing releases and attribution

  • Accept up to 20 neighboring deployments through otherReleases.
  • Mark an observed change as confounded when another release overlaps the comparison windows.
  • Keep evidenceVerdict available so clients can distinguish the observed signal from the attribution limit.
  • Recommend supplying release history when competing-deployment context is unknown.

Compact by default, detailed on demand

  • Return the verdict, confidence, traffic pattern, performance state, exact periods, sample readiness, attribution context, and recommended checks in the default response.
  • Avoid page, referrer, device, channel, and event breakdown fan-out in summary mode.
  • Preserve the complete evidence payload behind detailLevel: "full".
  • Update the guided release-impact prompt to request summary mode first and drill down only when needed.

Safety and data quality

  • All 37 tools remain read-only.
  • Equal pre/post durations and explicit comparison periods remain part of every release analysis.
  • Performance regressions and improvements still require material movement and sufficient samples.
  • Human-traffic referrer exclusions remain aligned across traffic and performance where Umami supports the same scope.
  • The result continues to describe before/after association rather than claiming causation.

Upgrade

npx --yes --prefer-online umami-compass@latest

Pin this exact release when reproducibility matters:

npx --yes umami-compass@0.4.0

Restart the MCP process or client after upgrading so it discovers the updated tool schema.

Compatibility and verification

  • Umami Cloud and self-hosted Umami 3.2+.
  • Node.js 22 or newer.
  • 105 automated tests plus lint, typecheck, build, package smoke testing, and CI on Node.js 22, 24, and 26.
  • Packed-package verification covers CLI version, MCP initialization, and the 14-tool default surface.
  • Official MCP Registry metadata validation completed before publication.
  • npm publication includes SLSA provenance.

Release links

Assets 2
Loading