Skip to content

v0.1.25.36 — committed + opt-in metadata on listReservations (rolls up .35 retired-keys hardening)

Choose a tag to compare

View all tags
@amavashev amavashev released this 19 Jun 15:36
· 174 commits to main since this release
v0.1.25.36
9665df9
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Rolls up two changes merged since v0.1.25.34.

v0.1.25.36 — committed + opt-in metadata on listReservations (#201)

GET /v1/reservations list rows now surface the same settlement detail as the single-row GET /v1/reservations/{id}, closing the projection gap reported in #201 (follow-up to #197). Implements cycles-protocol v0.1.25.8 (cycles-protocol#115).

  • committed (the COMMIT charge) is now returned unconditionally on COMMITTED list rows — a small scalar, on the same footing as finalized_at_ms.
  • metadata (reserve-time) and committed_metadata (commit-time) are arbitrary-size, possibly-PII maps, so they stay off list rows by default and are projected only when the caller opts in via a new include query parameter: GET /v1/reservations?include=metadata,committed_metadata.
  • include is projection-only — it does not affect row matching, ordering, or pagination, and is deliberately excluded from the cursor/filter hash, so changing it mid-pagination never invalidates a cursor. Unrecognized / empty tokens are ignored without error.

Compatibility: fully additive. Optional response fields + an additive, ignore-if-unrecognized query parameter; NON_NULL keeps the wire shape unchanged for callers that don't read them.

v0.1.25.35 — loud error when a retired-keys config is unusable (#200)

Hardens the v0.1.25.33 signer-key rotation-history publication. If cycles.evidence.signing.retired-keys is configured but produces zero publishable entries (so the active-key nbf clamp has nothing to bind against), the server now logs a clear ERROR naming the consequence — distinguishing "not configured" (legitimate, silent) from "configured but nothing publishable." The decision is based on what the JWK Set actually publishes, not parser output. Deliberately never fail-closed: the active key still publishes (refusing would break verification of all current evidence). Observability-only — no wire/spec change, no change to the published JWK Set.

Wire format stable within 0.1.x. Full engineering history in AUDIT.md.

Assets 2
Loading