GiteaInstall

Overview

This node operation deletes a specific package from a Gitea instance via its API. It is useful when you need to remove outdated, deprecated, or unwanted packages from your repository management system to keep it clean and organized.

Practical examples include:

• Removing a package version that contains critical bugs.
• Cleaning up old package versions no longer in use.
• Automating package lifecycle management by deleting packages after deployment or testing.

Properties

Output

The node outputs JSON data representing the response from the Gitea API after attempting to delete the specified package version. Typically, this will confirm successful deletion or provide error details if the operation failed.

No binary data output is expected from this operation.

Dependencies

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

Troubleshooting

• Common issues:

  • Incorrect or missing package details (owner, type, name, version) will cause the deletion to fail.
  • Insufficient permissions or invalid API token can result in authorization errors.
  • Network connectivity problems to the Gitea server will prevent the request from completing.

• Error messages:

  • 404 Not Found: The specified package or version does not exist. Verify the input properties.
  • 401 Unauthorized: Authentication failed. Check the API token and credentials setup.
  • 400 Bad Request: Invalid input parameters. Ensure all required fields are correctly filled.

Resolving these typically involves verifying the input values, checking API credentials, and ensuring network access to the Gitea server.

Links and References

• Gitea API Documentation
• n8n Documentation on HTTP Request Nodes (for understanding API interactions)