/gitlab/projects/releases

POST /api/gitlab/projects/releases

Price: 1 credit

List releases of a GitLab project by numeric id, 'namespace/project' path, or project URL

How to use it

List releases of a GitLab project by numeric id, 'namespace/project' path, or project URL. Each release includes tag, name, release notes, creation and release timestamps, author, the associated commit, and downloadable assets (source archives and asset links).

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• project string required — Project numeric id, 'namespace/project' path, or project URL (examples: "gitlab-org/gitlab-runner", "250833", "https://gitlab.com/gitlab-org/gitlab-runner"; minLength: 1)
• count integer required — Max number of releases to return (min: 1)

Response

• @type string (default: "GitlabRelease")
• tag string required
• name string nullable
• description string nullable
• created_at string (default: "")
• released_at string (default: "")
• upcoming_release boolean (default: false)
• author object nullable
  • @type string (default: "GitlabReleaseAuthor")
  • id integer required
  • username string (default: "")
  • name string (default: "")
  • state string (default: "")
  • image string nullable
  • web_url string (default: "")
• commit object nullable
  • @type string (default: "GitlabReleaseCommit")
  • id string (default: "")
  • short_id string (default: "")
• assets object nullable
  • @type string (default: "GitlabReleaseAssets")
  • count integer (default: 0)
  • sources array (default: [])
    • @type string (default: "GitlabReleaseAssetSource")
    • format string (default: "")
    • url string (default: "")
  • links array (default: [])
    • @type string (default: "GitlabReleaseAssetLink")
    • id integer nullable
    • name string (default: "")
    • url string (default: "")
    • direct_asset_url string nullable
    • link_type string (default: "")

Errors

• 422 — The request body did not validate Check the fields against this schema. A URN with the wrong prefix is the most common cause.
• 408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.
• 412 — Project not found or releases unavailable Retrying will not help: either the entity does not exist, or the input points at a different one.
• 429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.
• 500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.
• 529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.

Response headers

• X-Error — Error message text (present only on error)
• X-Request-ID — Unique request identifier
• X-Execution-Time — Execution time in seconds
• X-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.
• X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.
• X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.
• X-Retry-After — Seconds to wait before retrying. Present only on 429.