---
title: "Publish a draft"
description: "Refused (412 checks_not_green, with `checks`) when the commit's\nrequired checks are red or missing, unless `force`; the same rule as\nmerge, and anyone who may merge may publish. The tag is made at the\nrelease's commit when it does not exist (409 tag_exists when it names\nanother commit), and from then on git can't move or delete it.\n"
---

> Documentation Index
> Fetch the complete documentation index at: https://docs.gitpando.com/llms.txt
> Use this file to discover all available pages before exploring further.

Path: Pando API › releases

`POST /v1/monorepos/{owner}/{monorepo}/repos/{repo}/releases/{tag}/publish`

Refused (412 checks_not_green, with `checks`) when the commit's
required checks are red or missing, unless `force`; the same rule as
merge, and anyone who may merge may publish. The tag is made at the
release's commit when it does not exist (409 tag_exists when it names
another commit), and from then on git can't move or delete it.

## Authentication

Requires one of the following:

- `credential`, http, header `Authorization`
- `session`, apiKey, in cookie

## Path parameters

- `publishRelease.path.owner` (string, required) — The monorepo's owner, a namespace (a person's login or an organization). Matched without case.
  - pattern `^[a-z0-9](?:[a-z0-9]|-(?=[a-z0-9])){0,38}$`
- `publishRelease.path.monorepo` (string, required) — The monorepo's name within its owner (or an old name). Matched without case.
  - pattern `^[a-z0-9](?:[a-z0-9._]|-(?!-)){0,38}$`
- `publishRelease.path.repo` (string, required) — The repo's `name` (`projects-web`).
- `publishRelease.path.tag` (string, required)

## Request body

- `publishRelease.force` (boolean, optional)
  - default `false`

## Example request

```json
{
  "force": false
}
```

## Code samples

### cURL

```curl
curl --request POST \
  --url https://app.gitpando.com/v1/monorepos/string/string/repos/string/releases/string/publish \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '{
  "force": false
}'
```

### TypeScript

```typescript
const url = 'https://app.gitpando.com/v1/monorepos/string/string/repos/string/releases/string/publish';
const options = {
  method: 'POST',
  headers: {'Content-Type': 'application/json', Authorization: 'Bearer <token>'},
  body: JSON.stringify({force: false})
};

fetch(url, options)
  .then(res => res.json())
  .then(json => console.log(json))
  .catch(err => console.error(err));
```

### Python

```python
import requests

url = "https://app.gitpando.com/v1/monorepos/string/string/repos/string/releases/string/publish"

payload = { "force": False }
headers = {
    "Content-Type": "application/json",
    "Authorization": "Bearer <token>"
}

response = requests.post(url, json=payload, headers=headers)

print(response.text)
```

## Responses

### 200

Published

#### Example

```json
{
  "repo": "string",
  "tag": "string",
  "sha": "string",
  "title": "string",
  "notes": "string",
  "draft": true,
  "forced": true,
  "created_by": "string",
  "created_at": "2019-08-24T14:15:22Z",
  "updated_at": "2019-08-24T14:15:22Z",
  "published_by": "string",
  "published_at": "2019-08-24T14:15:22Z",
  "files": [
    {
      "name": "string",
      "size": 0,
      "sha256": "string",
      "content_type": "string",
      "uploaded_by": "string",
      "uploaded_at": "2019-08-24T14:15:22Z"
    }
  ],
  "checks": {
    "sha": "string",
    "state": "success",
    "required": [
      "string"
    ],
    "checks_unknown": "string",
    "missing": [
      "string"
    ],
    "statuses": [
      {
        "sha": "string",
        "context": "string",
        "state": "pending",
        "target_url": "string",
        "description": "string",
        "creator": "string",
        "app": "string",
        "created_at": "2019-08-24T14:15:22Z"
      }
    ]
  }
}
```

- `publishRelease.response.200.repo` (string, required)
- `publishRelease.response.200.tag` (string, required)
- `publishRelease.response.200.sha` (string, required) — Its commit
- `publishRelease.response.200.title` (string, required)
- `publishRelease.response.200.notes` (string, required) — Markdown
- `publishRelease.response.200.draft` (boolean, required)
- `publishRelease.response.200.forced` (boolean, required) — Published past red or missing required checks.
- `publishRelease.response.200.created_by` (string, required)
- `publishRelease.response.200.created_at` (string, required)
  - format `date-time`
- `publishRelease.response.200.updated_at` (string, required)
  - format `date-time`
- `publishRelease.response.200.published_by` (string | null, required)
- `publishRelease.response.200.published_at` (string | null, required)
  - format `date-time`
- `publishRelease.response.200.files` (array<object>, required)
  - `publishRelease.response.200.files.name` (string, required)
  - `publishRelease.response.200.files.size` (integer, required)
  - `publishRelease.response.200.files.sha256` (string, required)
  - `publishRelease.response.200.files.content_type` (string, required)
  - `publishRelease.response.200.files.uploaded_by` (string, required)
  - `publishRelease.response.200.files.uploaded_at` (string, required)
    - format `date-time`
- `publishRelease.response.200.checks` (object, optional) — Its commit's checks; on getRelease only.
  - `publishRelease.response.200.checks.sha` (string | null, required)
  - `publishRelease.response.200.checks.state` (string, required) — `success` when the merge gate passes; `missing` when a required context has not reported; `unknown` while the required checks are (an unforced merge is refused).
    - one of `"success"`, `"pending"`, `"failure"`, `"error"`, `"missing"`, `"unknown"`
  - `publishRelease.response.200.checks.required` (array | null, required) — Null while unknown.
  - `publishRelease.response.200.checks.checks_unknown` (string | null, required) — Why the required checks are unknown, in plain words: "Pando couldn't read this monorepo's required checks; try again", or "pando.toml line 3: expected comma or end of structure; fix it on main, or merge with force". Null otherwise.
  - `publishRelease.response.200.checks.statuses` (array<object>, required) — The latest status per context.
    - `publishRelease.response.200.checks.statuses.sha` (string, required)
    - `publishRelease.response.200.checks.statuses.context` (string, required)
    - `publishRelease.response.200.checks.statuses.state` (string, required)
      - one of `"pending"`, `"success"`, `"failure"`, `"error"`
    - `publishRelease.response.200.checks.statuses.created_at` (string, required)
      - format `date-time`
    - `publishRelease.response.200.checks.statuses.target_url` (string | null, optional)
    - `publishRelease.response.200.checks.statuses.description` (string | null, optional)
    - `publishRelease.response.200.checks.statuses.creator` (string, optional) — The member who posted it (a login); `app:<slug>` for a status posted with a status token or by a CI integration; `hook:<hook id>` for a status token from a web hook with no app.
    - `publishRelease.response.200.checks.statuses.app` (string | null, optional) — The CI service that reported it (`buildkite`, `github-actions`, ...), stamped by Pando from a status token or a CI integration, never from the body or `target_url`. Null when a member posted it with their own credential. The web shows the service's mark for a slug it knows.
  - `publishRelease.response.200.checks.missing` (array<string>, optional)


Source: https://docs.gitpando.com/api/releases/publishRelease/index.md