GitLab API

GitlabTool
Join our community

Actions905

Overview

This node operation updates a specific dist-tag for an NPM package within a GitLab group. It is useful for managing package versions and tags in a GitLab-hosted NPM registry, allowing users to set or change the distribution tag (like 'latest' or 'beta') for a package version. For example, a developer can use this to promote a beta version to the latest tag or to fix a tag pointing to an incorrect version.

Use Case Examples

  1. Updating the 'latest' dist-tag of an NPM package to a new version in a GitLab group.
  2. Changing a package's dist-tag from 'beta' to 'stable' to reflect release status.

Properties

Name Meaning
Skip Authentication Whether to skip authentication for the request (boolean). Defaults to false.
Authentication The authentication method used, defaulting to GitLab API key authentication. Hidden if Skip Authentication is true.
baseUrl The base URL of the GitLab instance, defaulting to https://gitlab.com.
Method HTTP method for the request, defaulting to PUT. Options include GET, POST, PUT, DELETE, HEAD, PATCH.
Path Parameters Parameters for the API path including: 'id' (the ID or URL-encoded path of the group) and 'tag' (the package dist-tag to update).

Output

JSON

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

Dependencies

  • Requires GitLab API key credential for authentication unless Skip Authentication is enabled.

Troubleshooting

  • Ensure the 'id' path parameter correctly identifies the GitLab group; incorrect IDs will cause 404 errors.
  • Verify the 'tag' parameter matches an existing or valid dist-tag; invalid tags may cause API errors.
  • Authentication errors may occur if the GitLab API key is missing or invalid; check credentials configuration.
  • Network or base URL misconfiguration can cause connection failures; verify the 'baseUrl' is correct.

Links

Discussion