GiteaInstall

Overview

This node interacts with a Gitea instance via its API to delete a specific release from a repository. It is useful in scenarios where you need to programmatically manage repository releases, such as cleaning up outdated or incorrect releases, automating release lifecycle management, or integrating release deletion into CI/CD pipelines.

For example, if a release was published by mistake or contains errors, this node can be used to remove it automatically without manual intervention through the Gitea web interface.

Properties

Output

The node outputs JSON data representing the response from the Gitea API after attempting to delete the release. Typically, for a delete operation, the output may be an empty object or confirmation of success. No binary data is produced by this node.

Dependencies

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

Troubleshooting

• Common issues:

  • Incorrect owner or repository name leading to "Not Found" errors.
  • Invalid or missing release ID causing failure to locate the release.
  • Insufficient permissions or invalid API token resulting in authorization errors.
  • Network connectivity problems preventing API communication.

• Error messages and resolutions:

  • 404 Not Found: Verify that the owner, repo, and release ID are correct and exist.
  • 401 Unauthorized or 403 Forbidden: Check that the API token has sufficient permissions and is valid.
  • Network errors: Ensure the Gitea server URL is reachable and no firewall blocks the request.

Links and References

• Gitea API Documentation - Releases
• Gitea Official Website