GitLab API icon

GitLab API

Gitlab

Actions917

Overview

This node operation updates a specific dist-tag of an NPM package in the GitLab package registry via the GitLab API. It is useful for managing package versions and tags programmatically, such as promoting a version to 'latest' or other custom tags. For example, a developer can automate updating the 'beta' tag of a package to point to a new version after a successful build.

Use Case Examples

  1. Updating the 'latest' dist-tag of an NPM package to a new version after publishing.
  2. Changing a package's 'beta' tag to point to a newly released beta version.

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, defaulting to https://gitlab.com.
Method The HTTP method used for the request, default is PUT for this operation.
Tag The dist-tag of the NPM package to update, e.g., 'latest' or 'beta'.

Output

JSON

  • response - The JSON response from the GitLab API after updating the package dist-tag, typically including the updated tag information.

Dependencies

  • GitLab API authentication credential

Troubleshooting

  • Ensure the 'tag' path parameter is provided and correctly matches an existing dist-tag.
  • Verify that the authentication credentials are valid and have permission to update package tags in the GitLab instance.
  • Check that the baseUrl is correct if using a self-hosted GitLab instance.
  • Common error messages include 401 Unauthorized (invalid credentials), 404 Not Found (package or tag does not exist), and 400 Bad Request (invalid request body).

Links

Discussion