GiteaInstall

Overview

This node interacts with a Gitea instance to manage repository releases. Specifically, the "Repo Delete Release By Tag" operation deletes a release identified by its tag name from a specified repository owned by a user or organization. This is useful for automating cleanup of outdated or incorrect releases in your repositories.

Practical examples include:

• Automatically removing a release after a failed deployment.
• Cleaning up test releases created during CI/CD pipelines.
• Managing release lifecycle by deleting deprecated versions programmatically.

Properties

Output

The node outputs JSON data representing the response from the Gitea API after attempting to delete the release. Typically, this will be an empty object or confirmation of deletion. No binary data output is expected.

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.

Troubleshooting

• Common issues:

  • Incorrect owner, repo, or tag values will cause the API call to fail.
  • Insufficient permissions or invalid API token will result in authorization errors.
  • Network connectivity problems to the Gitea server can cause request failures.

• Error messages and resolutions:

  • 404 Not Found: The specified release tag does not exist in the repository. Verify the tag name and repository details.
  • 401 Unauthorized or 403 Forbidden: Authentication failed or insufficient permissions. Check the API token and user rights.
  • Network errors: Ensure the Gitea server URL is correct and reachable from the n8n environment.

Links and References

• Gitea API Documentation - Releases
• Gitea Official Website