---
title: "Make an earlier release live"
description: "Makes a ready release live again, for rollback, by pointing the computer's edge route at that release's script; nothing is uploaded again."
canonical: "https://www.cool.computer/docs/api-reference/publishing/make-an-earlier-release-live"
---
# Make an earlier release live

> Makes a ready release live again, for rollback, by pointing the computer's edge route at that release's script; nothing is uploaded again.

```http
POST https://api.cool.computer/api/computers/{id}/releases/{number}/promote
```

Makes a ready release live again, for rollback, by pointing the computer's edge route at that release's script; nothing is uploaded again. A computer with a VM answers computer_has_vm, because its app directory is live; change its files with the files API or exec instead.

## Authorization

- A Cool Computers API key, user access token, or claimed agent access token in the Authorization header. Follow https://www.cool.computer/auth.md for agent registration and https://www.cool.computer/authentication.md for direct user credentials.

## Parameters

- `id` (path, string, at least 1 characters, required): The computer's name, such as agent-atlas, or its id (cmp_…). Every caller may use either, the computer's own runtime token included.
- `number` (path, integer, at least 1, required): Release number, starting at 1 for each computer.

## Responses

- `200`: The receipt of the live release.
  - `application/json` (object)
    - `release` (object, required)
      - `number` (integer, at least 1, required)
      - `state` ("uploading" or "ready" or "failed", required)
      - `live` (boolean, required)
      - `files` (integer, at least 0, required)
      - `bytes` (integer, int64, at least 0, required)
      - `created_at` (string, date-time, required)
      - `ready_at` (string, date-time)
    - `url` (string, uri, required): The computer's URL, which serves the live release.
    - `release_url` (string, uri): This release's own hostname r\<n>--\<name>. Absent once the computer's VM serves its URL.
    - `vm` (boolean, required): Whether the computer's VM serves its URL, because a server on it answered.
    - `next` (object, required): What to do next: upload the missing hashes, finalize, or nothing (done).
      - `action` ("upload" or "finalize" or "done", required)
      - `upload` (object)
        - `method` ("PUT" or "POST", required)
        - `href` (string, required): API path; {sha256} stands for each missing hash.
      - `finalize` (object)
        - `method` ("PUT" or "POST", required)
        - `href` (string, required): API path; {sha256} stands for each missing hash.
- `401`: Unauthorized.
- `403`: Forbidden.
- `404`: Not Found. `release_not_found` when the release does not exist.
- `409`: Conflict. `release_not_ready`, `computer_has_vm`: the computer has a VM and takes no release, or `publish_in_progress`. `job_taken_over`: as for POST /api/publish, after Operator took over your local agent session's comments job on the site.
- `429`: Too Many Requests. If the problem code is api_request_rate_exceeded, wait for Retry-After seconds; other problem codes describe a separate limit.
- `500`: Internal Server Error.
- `502`: Bad Gateway. `artifact_deploy_failed`: promote again.
- `503`: Service Unavailable. `artifacts_unavailable` means publishing is not configured on this server.
- `default`: A machine-readable API error with a stable code and recovery instruction.

An error is an `application/problem+json` document with a stable `code`; [API errors](/docs/api-reference/errors) says how to handle one.

## Example

```sh
curl -X POST "https://api.cool.computer/api/computers/$PARAM_ID/releases/$PARAM_NUMBER/promote" \
  -H "authorization: Bearer $TOKEN"
```
