Cashu Fault Lab
Browse documentation

Release

Release checklist

v0.3.0 publication checks and remaining external-validation blockers.

View sourceEdit on GitHub

These checks govern publication of the experimental developer CLI. They do not qualify a wallet for certification. Check the release commit's GitHub Actions results for their execution status.

Local and CI verification

  • Keep the npm manifest, generated adapter commands, website install command and release notes aligned at 0.3.0. Internal workspace and protocol versions remain independently versioned.
  • Run pnpm format:check, pnpm docs:cli:check, pnpm codegen:check, pnpm openapi:validate, pnpm typecheck, pnpm test, pnpm build, pnpm test:consumer and pnpm audit --prod.
  • Run PostgreSQL integration, funded delivery/lifecycle/doctor tests, both NIP-61 mint lanes, native Rust checks, the NUT-26 codec matrix, and installed-package tests.
  • Run website browser checks and keep public screenshots, artifacts and provenance aligned with 0.3.0.
  • Keep expected SDK gaps and blocked strict qualification visible; do not convert them into successful conformance claims.

Publication

  1. Merge the release PR after applicable CI passes.
  2. Tag that main commit v0.3.0. The existing publish workflow builds versioned public runtime images for amd64 and arm64, checks their source revision and platform manifests, and tests the installed CLI against those images.
  3. Let trusted publishing publish npm with provenance and create the GitHub release from these versioned notes. Verify that every publish job succeeds.
  4. Check the registry version and provenance, then run pinned doctor and demo commands from a clean public install. Retain redacted evidence and verify resource cleanup.

External validation blockers

  • Independent wallet receiver adoption and maintainer review beyond the bounded upstream fixture.
  • Independent ledger, mint and Lightning authorities for qualifying wallet evidence.
  • Two qualifying implementation pairs with independently verified source/build provenance and distinct mint identities.
  • Public-relay hardening and externally produced wallet-doctor captures.

These blockers prevent certification, not publication of the experimental developer preview.