GitHub App icon

GitHub App

Consume GitHub API using GitHub App authentication

Actions36

Release → Get

AI-generated

Overview

This node operation retrieves a specific release from a GitHub repository using GitHub App authentication. It is useful for scenarios where you need to fetch detailed information about a particular release by its ID, such as automation workflows that monitor or manage software releases in repositories. For example, it can be used to get release notes, version tags, or metadata for deployment pipelines or release tracking.

Use Case Examples

  1. Fetch details of a release by specifying the repository owner, repository name, and release ID to automate release management.
  2. Use in CI/CD workflows to retrieve release information and trigger subsequent deployment steps based on release data.

Properties

Name Meaning
Repository Owner The owner of the GitHub repository from which to get the release. It supports selection from a list, URL input, or direct name input.
Repository Name The name of the GitHub repository containing the release. It supports selection from a list, URL input, or direct name input.
Release ID The unique identifier of the release to retrieve. This is required to specify which release to get.

Output

JSON

  • id - The unique identifier of the release.
  • tag_name - The tag name associated with the release.
  • name - The name of the release.
  • body - The description or release notes of the release.
  • draft - Indicates if the release is a draft (unpublished).
  • prerelease - Indicates if the release is a prerelease (non-production ready).
  • created_at - The creation timestamp of the release.
  • published_at - The publication timestamp of the release.
  • author
    • login - The GitHub username of the author who created the release.

Dependencies

  • GitHub API access via GitHub App authentication

Troubleshooting

  • Ensure the Release ID is correctly specified; an invalid or missing ID will cause errors.
  • Verify that the repository owner and repository name are correct and accessible with the provided GitHub App credentials.
  • Check that the GitHub App has the necessary permissions to access release information in the repository.
  • Common error messages include 404 Not Found if the release or repository does not exist, or authentication errors if the GitHub App token is invalid or expired.

Links

Discussion