GitLab API icon

GitLab API

Gitlab

Actions917

Overview

This node operation updates a release associated with a specific Git tag in a GitLab project using the GitLab API. It is useful for managing project releases programmatically, such as modifying release notes or metadata for a given tag. For example, a user can update the release description or assets for a particular version of their software hosted on GitLab.

Use Case Examples

  1. Updating the release notes for version 1.0.0 of a project.
  2. Changing the release assets associated with a specific Git tag.

Properties

Name Meaning
Skip Authentication Whether to skip authentication for the API request.
Authentication The authentication method used for the API request, typically an API key credential.
baseUrl The base URL of the GitLab instance to which the request is sent.
Method The HTTP method used for the request, default is PUT for this operation.
Path Parameters Parameters included in the request path to identify the project and release tag.

Output

JSON

  • id - The unique identifier of the release.
  • tag_name - The Git tag name associated with the release.
  • description - The description or notes of the release.
  • created_at - Timestamp when the release was created.
  • updated_at - Timestamp when the release was last updated.
  • assets - Assets associated with the release, such as links to binaries or source code.

Dependencies

  • GitLab API authentication token or credentials

Troubleshooting

  • Ensure the project ID and tag name are correctly specified and URL-encoded if necessary.
  • Verify that the authentication token has sufficient permissions to update releases in the project.
  • Check the base URL to ensure it points to the correct GitLab instance.
  • Common error messages include 404 Not Found if the project or tag does not exist, and 401 Unauthorized if authentication fails.

Links

Discussion