Gitea icon

Gitea

Interact with Gitea via API

Actions393

Overview

This node enables creating a new release in a specified repository on a Gitea server via its API. It is useful for automating the release management process, such as tagging versions, publishing draft or prerelease versions, and adding descriptive notes to releases.

Common scenarios include:

  • Automatically creating a release when code is merged into a main branch.
  • Tagging a specific commit with a release version.
  • Managing draft or prerelease states programmatically during CI/CD workflows.

Example: After pushing code changes, this node can create a release tagged "v1.0.0" with release notes, marking it as a prerelease or draft depending on your workflow needs.

Properties

Name Meaning
Owner The owner (user or organization) of the repository where the release will be created.
Repo The name of the repository to create the release in.
Tag Name The name of the tag for this release (e.g., "v1.0.0").
Target Commitish The commitish value that determines where the Git tag is created from (branch, SHA).
Name The name of the release.
Body The description or release notes for the release.
Draft Boolean indicating if the release should be created as a draft (not published yet).
Prerelease Boolean indicating if the release is a prerelease (e.g., beta or RC version).

Output

The node outputs JSON data representing the newly created release object returned by the Gitea API. This typically includes details such as:

  • Release ID
  • Tag name
  • Release name
  • Description/body
  • Draft and prerelease status
  • URLs related to the release (e.g., HTML URL)
  • Timestamps for creation and publication

No binary data output is involved.

Dependencies

  • Requires connection to a Gitea instance with appropriate API access.
  • Needs an API authentication token credential configured in n8n to authorize requests.
  • The base URL for the Gitea API must be set in the credentials.

Troubleshooting

  • Authentication errors: Ensure the API token has sufficient permissions to create releases in the target repository.
  • Repository not found: Verify the owner and repo names are correct and accessible by the authenticated user.
  • Invalid tag name: The tag name must follow Git tag naming conventions; invalid characters may cause errors.
  • Network issues: Confirm the Gitea server URL is reachable from the n8n environment.
  • Draft/Prerelease flags: If unexpected release visibility occurs, double-check the boolean values for draft and prerelease properties.

Links and References

Discussion