Skip to content

v1.1.0

Choose a tag to compare

View all tags
@github-actions github-actions released this 25 Sep 18:41
· 14 commits to main since this release
v1.1.0
06b0087
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Post-v1 integration and operations release. v1.1.0 adds narrowly scoped Cloudflare retry ergonomics and MCP operation-identity guidance without changing the frozen accounting lifecycle or persisted Store contracts.

Added

  • Added privacy-bounded, best-effort operational telemetry for Cloudflare exact retries (retry.scheduled, retry.recovered, retry.failed) without exposing usage identities, endpoints, or raw errors (#239).
  • Added optional mcp-usage-control-cloudflare/exact-retry support for bounded exact replay of scalar markLiable(), renew(), and settle() after retryable transport failures, while initial reserve, growth, and vector transitions remain single-attempt (#232).

Changed

  • Hardened the Cloudflare exact-retry helper with bounded exponential equal-jitter backoff between eligible attempts, added exact-subpath checks to the GitHub Release packed-byte smoke, and moved the development test runner to patched Vitest 4.1.11 with source-only test discovery (#237).
  • Recorded the MCP single-round read operation-identity decision: no weak JSON-RPC/session-derived dedup helper is added; applications without a retry-stable logical key should use a fresh server-side ID per dispatch, while products that need retry-stable metering must provide an explicit validated logical action ID (#233).

Release boundary

  • Keeps the v1 reserve -> liability -> grow -> renew -> settle accounting model, replay scope, provider storage contracts, and Node.js 22+ runtime floor unchanged.
  • Keeps ambiguous initial Cloudflare reserve recovery explicit through read-only reconciliation; v1.1.0 does not introduce blind reserve retry.
  • Aligns all five public package manifests at 1.1.0; supported release evidence remains Node.js 22/24 with the aggregate test (22) gate.
  • This GitHub/source release does not itself publish to npm. Registry publication remains a separate manually authorized Trusted Publishing workflow using the exact validated GitHub Release tarballs.

The attached .tgz files are the exact package artifacts validated by this release workflow. Verify them with SHA256SUMS and GitHub artifact attestations. Their presence does not mean the packages were published to npm; registry publication remains separately authorized.

Assets 8
Loading