Configure Milestone stages

PUT/api/v1/workspaces/{workspace_id}/milestone-lifecycle

Requires workspace:manage. Atomically replaces the bounded catalog under If-Match. Every semantic category retains active coverage. Referenced IDs and categories cannot be removed or changed. Archiving an in-use stage requires a same-category active replacement; at most 1000 active Milestones are moved atomically. Archived Milestones retain historical selections. Conflicts include revision_conflict, milestone_stage_in_use and lifecycle_migration_too_large. Names are trimmed; no transition graph is introduced.

Path Parameters

workspace_idRequired

string <uuid>

Example0198ac5e-f9b7-7000-8000-000000000001

Header Parameters

X-CSRF-TokenRequired

string·min 43·max 43

Session-bound CSRF token. It must exactly match the __Host-assign_csrf cookie sent with the request.

Idempotency-KeyRequired

string·min 16·max 200

Opaque client-generated key for safely retrying this operation.

If-MatchRequired

string

Entity tag containing the resource version last observed by the client.

Request Body

application/json

stagesRequired

object[]·min 4·max 100

replacements

object

Source stage ID to same-category active replacement stage ID for atomic archival migration.

Responses

Authentication · Conventions and errors · API guides · Resource reference

Configure Milestone stages