GiteaInstall

Overview

This node allows users to edit an existing release in a repository hosted on a Gitea server via its API. It is useful for automating the management of software releases, such as updating release notes, changing tags, or modifying release states (draft/prerelease). For example, a developer can update the description and tag of a release after fixing bugs or adding features without manually navigating the Gitea web interface.

Properties

Output

The node outputs JSON data representing the updated release object returned by the Gitea API. This typically includes fields such as the release ID, tag name, name, body, draft status, prerelease status, target commitish, creation and update timestamps, and URLs related to the release.

No binary data output is involved.

Dependencies

• Requires access to a Gitea instance with API enabled.
• Needs an API authentication token credential configured in n8n to authorize requests.
• The base URL of the Gitea server must be provided in the credentials configuration.

Troubleshooting

• Common issues:

  • Invalid or missing repository owner or name will cause the API call to fail.
  • Providing an incorrect release ID will result in a "release not found" error.
  • Insufficient permissions or invalid API token will lead to authorization errors.
  • Malformed input data (e.g., invalid tag name format) may cause validation errors.

• Error messages and resolutions:

  • 404 Not Found: Check if the repository owner, repo name, and release ID are correct.
  • 401 Unauthorized: Verify that the API token is valid and has sufficient permissions.
  • 400 Bad Request: Ensure all required fields are correctly formatted and valid.
  • Network errors: Confirm the Gitea server URL is reachable from the n8n environment.

Links and References

• Gitea API Documentation - Releases
• Gitea Official Website
• n8n Documentation - Creating Custom Nodes