Sardis

Sardis v0.8.2: Release Readiness Hardening for MCP + SDKs

v0.8.2 hardens release scripts, isolates protocol conformance lanes, and improves local validation when npm or network access is constrained.

v0.8.2 is an engineering-readiness release focused on reproducible checks and safer pre-prod execution. We hardened release scripts, isolated protocol conformance lanes, and made local validation clearer when npm or network access is constrained.

What Changed

  • Deterministic JS bootstrap preflight -- bootstrap:js now checks node/pnpm versions, DNS resolution, and npm registry reachability before install.
  • Live-chain conformance gate added -- check:live-chain validates Turnkey + testnet integrations and supports strict fail-closed mode.
  • Protocol lane isolation fixed -- Root conformance and package-level UCP tests now run without pytest import collisions.
  • Conformance reporting hardened -- Report generation now works even without pytest JSON plugins, with summary-based pass/fail extraction.

Why This Release Matters

Design partner programs fail when local and CI outcomes diverge. v0.8.2 reduces that risk by making release checks explicit, deterministic, and transparent under both normal and constrained environments.

  • Faster diagnosis when local npm execution is blocked by DNS/network policy
  • Safer progression from protocol conformance to real integration checks
  • Clearer release gating semantics for staging and design-partner readiness

Current Validation Baseline

  • Protocol conformance: 191 passed / 0 failed / 0 skipped
  • Python SDK suite: 251 passed / 4 skipped
  • A2A + UCP package suites: 98 + 53 passed

See the Changelog for the next hardening steps.