---
title: "Update the rolling release settings for the project"
method: PATCH
path: "/v1/projects/{idOrName}/rolling-release/config"
tags: ["rolling-release"]
---

# Update the rolling release settings for the project

`PATCH /v1/projects/{idOrName}/rolling-release/config`

Update (or disable) Rolling Releases for a project. When disabling with the resolve-on-disable feature flag enabled, any active rolling release document is resolved using the disableRolloutAction parameter: "abort" to roll back (default), or "complete" to promote the canary to production. When enabling or updating config, changes only affect the next production deployment and do not alter a rollout that's already in-flight. Note: Enabling Rolling Releases automatically enables skew protection on the project with the default value if it wasn't configured already.

## Path parameters

- `idOrName` string, required — Project ID or project name (URL-encoded)

## Query parameters

- `teamId` string
- `slug` string

## Response `200`

- union
  - object
    - `rollingRelease` unknown, required
  - object
    - `rollingRelease` object, nullable, required
      - `stages` object[], nullable
        - `targetPercentage` number, required — The percentage of traffic to serve to the canary deployment (0-100)
        - `requireApproval` false | true — Whether or not this stage requires manual approval to proceed
        - `duration` number — Duration in minutes for automatic advancement to the next stage
        - `linearShift` false | true — Whether to linearly shift traffic over the duration of this stage

## Other responses

- `400` — One of the provided values in the request query is invalid.
- `401` — The request is not authorized.
- `403` — You do not have permission to access this resource.
- `404`
- `410`

---

[API](https://skmtc.net/vercel/apis/api.md) · [All operations](https://skmtc.net/vercel/apis/api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/vercel/api/versions/61d1ba3f6dac/schema)