Sign in
latestOpenAPI 3.0.32026-08-227451,2751.8 MB

d0fc0114da66

LinkMablnet

Publish a new mablnet worker release (operator / release CI)

Stores a signed release manifest and initialises the channel's rollout. The request body is the signed manifest produced by the release pipeline (see link/mablnet/docs/deployment/release-pipeline.md § Aggregate job). The api derives channel and version from the manifest, stores the manifest verbatim, sets the channel's current_version to the new version and fallback_version to the prior current, and applies the default staged rollout schedule (1% → 10% → 50% → 100% over 24h). Auth: a release-engineering identity, not an interactive customer. The publishing principal is CI rather than a user-OAuth admin, so the exact machine-auth shape is an open api-team decision — see design doc § Release-publisher auth.

post/link/mablnet/releases

Request body

manifeststring required

Base64 of the exact signed manifest bytes. Decode, then verify + parse per manifest-format.md.

Response

Release stored; the resulting channel rollout state is returned.

idstring

Datastore key for this entity — equals channel (one entity per channel). Server-set.

channelstring required

Release channel this state governs.

current_versionstring required

The version being rolled out to (Hosts inside the rolled-out percentage receive this).

fallback_versionstring

What Hosts not yet inside the rollout receive. Unset once a rollout reaches 100% and the current version is fully rolled out.

force_percentinteger

When set, overrides the time-based schedule with an explicit rolled-out percentage (operator force-advance). Cleared by resuming the schedule.

published_atstring date-time

When the current rollout started; the schedule's since_ms offsets are relative to this.

pausedboolean required

When true, the manifest endpoint stops advancing the rollout — Hosts stay on whichever version they have.