Override Release Decision — POST /api/v1/release-readiness/{run_id}/override

Override Release Decision

Override the AI release decision (QA Lead only). Records the override in an immutable audit trail with before/after values.

Endpoint: POST /api/v1/release-readiness/{run_id}/override

Authentication: Send a signed-in user’s access token in Authorization: Bearer <access token>, or an API key in X-API-Key: <API key>.

• Your role must be QA lead or higher.
• You must have access to this test run.

Parameters

Name	In	Required	Type	Default	Description
run_id	path	yes	string (uuid)
X-API-Key	header	no	string or null		API key, as an alternative to the access token (see Authentication).

Request body

Content type	Body	Required
application/json	ReleaseCouncilOverrideRequest	yes

Responses

Status	Meaning	Body
200	Successful Response	ReleaseCouncilResponse (application/json)
422	Validation Error	HTTPValidationError (application/json)

Errors this endpoint returns, read from its source code:

• 404, with the message “No release decision found for this run”
• 422, with messages such as “Override reason is required”, “override_recommendation must be GO, NO_GO, or CONDITIONAL_GO”

It can also return 401 if your credential is missing or expired, 403 if your credential does not allow this request, and 404 if the item does not exist or you cannot see it. Your role, your project membership and the key’s scope decide what a credential allows. See Errors and retries.

More details

• Group: Release Readiness
• Operation ID: override_release_decision_api_v1_release_readiness__run_id__override_post
• Source code: backend/app/routers/release_readiness.py, line 105
• Specification: OpenAPI JSON