Results per page (max 100)
Default:30
Page number of the results to fetch.
Default:1
This returns a list of releases, which does not include regular Git tags that have not been associated with a release. To get a list of Git tags, use the Repository Tags API.
Information about published releases are available to everyone. Only users with push access will receive listings for draft releases.
Results per page (max 100)
Default:30
Page number of the results to fetch.
Default:1
Response
A release.
The name of the tag.
Example:v1.0.0
Specifies the commitish value that determines where the Git tag is created from.
Example:master
true to create a draft (unpublished) release, false to create a published one.
Example:false
Whether to identify the release as a prerelease or a full release.
Example:false
Simple User
Data related to a release.
Users with push access to the repository can create a release.
This endpoint triggers notifications. Creating content too quickly using this endpoint may result in secondary rate limiting. See “Secondary rate limits” and “Dealing with secondary rate limits” for details.
The name of the tag.
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 (usually master
).
The name of the release.
Text describing the contents of the tag.
true
to create a draft (unpublished) release, false
to create a published one.
Default:false
true
to identify the release as a prerelease. false
to identify the release as a full release.
Default:false
Response
A release.
The name of the tag.
Example:v1.0.0
Specifies the commitish value that determines where the Git tag is created from.
Example:master
true to create a draft (unpublished) release, false to create a published one.
Example:false
Whether to identify the release as a prerelease or a full release.
Example:false
Simple User
Data related to a release.
To download the asset’s binary content, set the Accept
header of the request to application/octet-stream
. The API will either redirect the client to the location, or stream it directly if possible. API clients should handle both a 200
or 302
response.
asset_id parameter
To download the asset’s binary content, set the Accept
header of the request to application/octet-stream
. The API will either redirect the client to the location, or stream it directly if possible. API clients should handle both a 200
or 302
response.
Data related to a release.
The file name of the asset.
Example:Team Environment
State of the release asset.
Allowed values:uploadedopen
Simple User
Users with push access to the repository can edit a release asset.
asset_id parameter
The file name of the asset.
An alternate short description of the asset. Used in place of the filename.
Example:"uploaded"
Response
Data related to a release.
The file name of the asset.
Example:Team Environment
State of the release asset.
Allowed values:uploadedopen
Simple User
asset_id parameter
Response