A release is the platform’s record that a process is serving a rollout — a rolloutId, optional changeId, and stampIds. Operators use that identity in the Fireweave console to reason about what is live.
The SDK releases namespace (setContext, start, complete, fail) was removed in v1 (ADR-0010). conformance/surface/control-points.surface.json asserts the client must not expose releases. There is no replacement call on the client. See Migrate 2.1 to 2.3. Why the concept still matters
A control-point read does not bind your process to a rollout. The console and fw-server still talk about rollouts, stamps, and attestation. That is platform work. The SDK’s job in v1 is to evaluate a control point and register a target.
Do not map console states (Registered / Ramping / Verifying / Rolled back) onto SDK methods. Those names were never SDK APIs, and they are not now.
How it relates
What replaced the client API
Nothing on the client. If your 2.1 code called client.releases.setContext / start / complete / fail, delete those calls. Boot attestation and rollout lifecycle live outside this SDK.
The spec/release-context.schema.json envelope still exists in the spec tree so the absence reads as scope, not oversight. The SDK does not expose it.
Last modified on September 11, 2026
