Create a release

Publish a release of a tag, with a title (release_name; name in the answer) and notes (body, Markdown).

POST/repos/{owner}/{name}/releases

A tag that does not exist yet is made at target (a branch or commit; the default branch when left out), as a lightweight tag, under the repository’s tag rulesets. draft keeps it from everyone without the Write role until it is published; prerelease marks it not ready for everyone, so it is never the latest. One release per tag. Needs the Write role.

A tag that already exists is released as it is, and target is ignored. One release per tag: releasing a tag again is refused with conflict.

Authentication: Required. Send an access token as Authorization: Bearer.
MCP tool: repository with action create_release, and the same inputs
Scope: An access token needs repo: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
`tag_name`	string	Yes	The tag to release, such as v1.2.0. Made at target when it does not exist yet.
`target`	string	No	A branch or commit to make a new tag at. The default branch when left out; ignored for a tag that exists.
`release_name`	string	No	Its title (name in the answer), at most 200 characters; under a repository’s address `name` is the repository’s. The tag’s name is shown when it has none.
`body`	string	No	Its notes, Markdown, at most 125,000 characters.
`draft`	boolean	No	Seen only by those with the Write role until published.
`prerelease`	boolean	No	Not ready for everyone: never the latest release.

Example request

curl -X POST https://api.g1t.sh/repos/flagon-io/hello/releases \
  -H "Authorization: Bearer $G1T_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "tag_name": "v1.2.0",
    "target": "main",
    "release_name": "Greetings by name",
    "body": "## What changed\n\n- `hello` greets the caller by name (#12)\n- Faster start-up (#15)",
    "draft": false,
    "prerelease": false
  }'

Example response

A successful request answers 200 with:

{
  "id": "rel_01m4a2b7c9d3e5f7g9h1j3k5m7",
  "tag_name": "v1.2.0",
  "target": "9f3c2a1b7e5d4c3b2a19f8e7d6c5b4a39281706f",
  "name": "Greetings by name",
  "body": "## What changed\n\n- `hello` greets the caller by name (#12)\n- Faster start-up (#15)",
  "draft": false,
  "prerelease": false,
  "author": "ada",
  "created_at": "2026-10-06T16:02:11.000Z",
  "published_at": "2026-10-06T16:02:11.000Z",
  "latest": true
}

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.