Evaluate Release Gate — POST /api/v1/releases/{release_id}/gate/evaluate
Evaluate Release Gate
Evaluate the gate and, by default, record the verdict.
Endpoint: POST /api/v1/releases/{release_id}/gate/evaluate
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 release.
Parameters
Section titled “Parameters”| Name | In | Required | Type | Default | Description |
|---|---|---|---|---|---|
release_id | path | yes | string | ||
record | query | no | boolean | true | Append the verdict to the release’s audit history. Pass false to preview without recording. |
X-API-Key | header | no | string or null | API key, as an alternative to the access token (see Authentication). |
Request body
Section titled “Request body”No request body.
Responses
Section titled “Responses”| Status | Meaning | Body |
|---|---|---|
200 | Successful Response | Not documented (application/json) |
422 | Validation Error | HTTPValidationError (application/json) |
Response fields not documented. The API specification does not describe the body of every response this endpoint returns, so this page cannot list those fields. The body is not empty. To see it, call the endpoint on your own installation. All endpoints with undocumented responses.
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
Section titled “More details”- Group: Releases
- Operation ID:
evaluate_release_gate_api_v1_releases__release_id__gate_evaluate_post - Source code:
backend/app/routers/releases.py, line 736 - Specification: OpenAPI JSON