Create a release
POST/api/repos/{owner}/{repo}/releases
createRepositoryRelease
Creates a release for a git tag that already exists in the repository. The tag is peeled to the commit it names and that commit is recorded; a tag that does not point at a commit is rejected rather than stored. A tag already released is 409, as is claiming the rolling slot when another release holds it. Callable with a CI job token of this repository from a trusted run (the release then records the workflow run rather than an account); a job token of a fork pull request run is 403.
Requires authentication using a bearer token or a session cookie — see tokens and scopes.
curl
curl -X POST 'https://neosource.dev/api/repos/OWNER/REPO/releases' \
-H 'Authorization: Bearer $NEOSOURCE_TOKEN' \
-H 'Content-Type: application/json' \
-d '{"tag":"v1.2.0"}'fetch
fetch("https://neosource.dev/api/repos/OWNER/REPO/releases", {
method: "POST",
headers: {
Authorization: "Bearer $NEOSOURCE_TOKEN",
"Content-Type": "application/json",
},
body: JSON.stringify({"tag":"v1.2.0"}),
});Path parameters
ownerrequiredRepository owner or organization slug.
reporequiredRepository name.
Request bodyrequired
application/json
Responses
201Release created
application/json
Standard errors
Bodies documented once for the whole API — see standard errors.
- 400Bad Request — one of: invalid_input
- 401Authentication required
- 403Forbidden — one of: forbidden
- 404Not Found — one of: not_found
- 409Conflict — one of: already_exists, conflict, non_fast_forward
- 423Locked — one of: busy
- 429Rate limited — retry after the `Retry-After` header
- 500Internal server error
- 503Service temporarily unavailable / at capacity — retry after the `Retry-After` header
- 504Gateway timeout — the request exceeded the server's handling budget