Integration release lifecycle

The Lifecycle

Transitions Explained

Registration records a validated release or publishes it immediately when requested. Staff can publish, deprecate and retire through guarded operations. A published manifest stays immutable through later status changes; identical redeployment only replaces runtime information.

What Cannot Happen

Publication freezes content, so registration cannot turn the release mutable again. Deprecation requires a published source release. A release must first be deprecated before staff can retire it. Staff publication requires validated status, so retired releases cannot be republished by that transition.

Concurrency and Timing

Registration and staff transitions commit atomically and existing release rows are locked. A concurrent insert of the same new version can lose to database uniqueness. Deprecation does not recompute the current pointer and there is no forced account upgrade timer.