Set artifact retention

Set how many days the repository keeps artifacts by default, and at most: days, from 1 to 90.

PUT/repos/{owner}/{name}/actions/permissions/artifact-and-log-retention

Artifacts already uploaded keep the expiry they were given. Needs the Maintain role.

Only artifacts uploaded afterwards are kept the new number of days. A workflow’s retention-days asks for fewer, never more.

Authentication: Required. Send an access token as Authorization: Bearer.
MCP tool: workflow with action set_artifact_retention, and the same inputs
Scope: An access token needs workflows:write.

Path parameters

Name	Type	Required	Description
`owner`	string	Yes	The workspace that owns the repository.
`name`	string	Yes	The repository’s name.

Body parameters

Send a JSON object. Names are snake_case, as in responses; the camelCase spelling is accepted too.

Name	Type	Required	Description
`days`	integer	Yes	Days to keep artifacts, by default and at most.

Example request

curl -X PUT https://api.g1t.sh/repos/flagon-io/g1t/actions/permissions/artifact-and-log-retention \
  -H "Authorization: Bearer $G1T_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "days": 30
  }'

Example response

A successful request answers 200 with:

{
  "days": 30,
  "maximum_allowed_days": 90
}

Errors

A failed request answers with one of these statuses and a body like {"error": {"code": "not_found", "message": "Repository not found."}}. See errors.

Status	Code	When
401	`unauthenticated`	A token is required, or the one sent is not valid.
403	`forbidden`	The token is valid but not allowed to do this, such as a member-only change or an agent token outside its repository.
404	`not_found`	It does not exist, or you cannot see it.
409	`conflict`	The request conflicts with the current state.
422	`invalid`	The input is not valid. `message` says which field and why.