Gitea icon

Gitea

Interact with Gitea via API
Join our community

Actions393

Overview

This node interacts with the Gitea API to list releases of a specified repository. It is useful for workflows that need to retrieve release information such as version tags, release notes, or metadata about published software versions in a Gitea repository. Typical use cases include automation pipelines that monitor new releases, generate changelogs, or trigger deployment processes based on release events.

Properties

Name Meaning
Owner The owner (user or organization) of the repository from which to list releases.
Repo The name of the repository to query for releases.
Draft Filter to include or exclude draft releases. If the user lacks write access to the repo, drafts will not be shown regardless.
Pre Release Filter to include or exclude pre-release versions.
Page The page number of results to return (1-based pagination).
Limit The number of results per page (page size).

Output

The node outputs JSON data representing the list of releases retrieved from the Gitea repository. Each release object typically contains details such as release ID, tag name, title, description, draft status, pre-release status, creation and publication dates, and associated assets. This structured output can be used downstream in workflows for further processing or notifications.

No binary data output is indicated by the source code.

Dependencies

  • Requires an API key credential for authenticating with the Gitea instance.
  • Needs the base URL of the Gitea server configured in credentials.
  • Uses the Gitea REST API v1 endpoint /api/v1 to fetch release data.

Troubleshooting

  • Common issues:

    • Incorrect or missing repository owner or name will result in errors or empty results.
    • Insufficient permissions may prevent viewing draft releases.
    • Pagination parameters (page and limit) set incorrectly might cause unexpected result sets or no data.
    • Network or authentication failures if the API key or base URL is misconfigured.

  • Error messages:

    • Authentication errors indicate invalid or missing API credentials.
    • "Not Found" errors usually mean the repository does not exist or the owner/repo names are incorrect.
    • Permission denied errors occur when the user lacks rights to view certain releases (e.g., drafts).

To resolve these, verify the input properties, ensure correct API credentials, and confirm repository access rights.

Links and References

Discussion