List Releases

github.list_releases
ActionBusiness appsconnection required

Calls the GitHub API GET /repos/{owner}/{repo}/releases.

List a repository's releases, newest first.

Connection

Required
Yes — the node will not save without one
Auth type
Bearer token
Providers
GitHub
Secret shape
the GitHub personal access token
Resolved by
config.connection_id, else node.connection_id, else the tenant's sole GitHub connection

Configuration

3 fields, 2 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.

FieldTypeRequiredDefaultConstraintsExample
owner
Repository owner — the user or organisation login. Supports {{ }}.
stringYes——octocat
repo
Repository name, without the owner prefix. Supports {{ }}.
stringYes——hello-world
max_items
Stop after this many rows; further pages are followed via the Link header.
numberNo1001–1000—

Example configuration

Every value below is the contract’s own example or default — nothing invented.

{
  "max_items": 100,
  "owner": "octocat",
  "repo": "hello-world"
}

Output

One shape.

result

FieldTypeExample
releases
The releases this step read.
array—
releases[].id
Release id, used by the asset endpoints.
number—
releases[].tag_name
Tag the release points at.
string—
releases[].name
Release title.
string—
releases[].draft
True while the release is unpublished.
boolean—
releases[].prerelease
True for a pre-release.
boolean—
releases[].html_url
Link to the release page.
string—
releases[].published_at
When it was published, ISO 8601.
string—
count
How many rows this step returned.
number—
{
  "count": 0,
  "releases": [
    {
      "draft": false,
      "html_url": "",
      "id": 0,
      "name": "",
      "prerelease": false,
      "published_at": "",
      "tag_name": ""
    }
  ]
}

See List Releases run in a workflow.

In a technical demo we add the GitHub connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.