PATCH /repos/{owner}/{repo}/releases/{release_id}

Users with push access to the repository can edit a release.

Servers

Path parameters

Name Type Required Description
repo String Yes

The name of the repository without the .git extension. The name is not case sensitive.

release_id Integer Yes

The unique identifier of the release.

owner String Yes

The account owner of the repository. The name is not case sensitive.

Request headers

Name Type Required Description
Content-Type String Yes The media type of the request body.

Default value: "application/json"

Request body fields

Name Type Required Description
target_commitish String No

Specifies the commitish value that determines where the Git tag is created from. Can be any branch or commit SHA. Unused if the Git tag already exists. Default: the repository's default branch.

draft Boolean No

true makes the release a draft, and false publishes the release.

make_latest String No

Specifies whether this release should be set as the latest release for the repository. Drafts and prereleases cannot be set as latest. Defaults to true for newly published releases. legacy specifies that the latest release should be determined based on the release creation date and higher semantic version.

Possible values:

  • "false"
  • "legacy"
  • "true"

Default value: "true"

tag_name String No

The name of the tag.

name String No

The name of the release.

body String No

Text describing the contents of the tag.

prerelease Boolean No

true to identify the release as a prerelease, false to identify the release as a full release.

discussion_category_name String No

If specified, a discussion of the specified category is created and linked to the release. The value must be a category that already exists in the repository. If there is already a discussion linked to the release, this parameter is ignored. For more information, see "Managing categories for discussions in your repository."

How to start integrating

  1. Add HTTP Task to your workflow definition.
  2. Search for the API you want to integrate with and click on the name.
    • This loads the API reference documentation and prepares the Http request settings.
  3. Click Test request to test run your request to the API and see the API's response.