GitLab API

GitlabTool
Join our community

Actions1000

Overview

This node operation allows updating an NPM package in a specific GitLab project using the GitLab API. It is useful for managing package versions or metadata within a project's package registry. For example, a developer can update package details directly from an automation workflow without manually accessing the GitLab interface.

Use Case Examples

  1. Updating the metadata of an NPM package in a GitLab project to reflect new version information.
  2. Automating package updates in a CI/CD pipeline by modifying package details after a successful build.

Properties

Name Meaning
Skip Authentication Determines whether to skip authentication for the API request.
Authentication Specifies the authentication method to use, defaulting to GitLab API authentication.
baseUrl The base URL of the GitLab instance, defaulting to https://gitlab.com.
Method HTTP method to use for the request, default is GET but can be set to PUT for this operation.
Path Parameters Parameters to specify the project ID and the NPM package name to update.

Output

JSON

  • response - The JSON response from the GitLab API after updating the NPM package.

Dependencies

  • GitLab API authentication credential

Troubleshooting

  • Ensure the project ID and package name are correctly specified and URL-encoded if necessary.
  • Verify that the authentication credentials are valid and have sufficient permissions to update packages in the project.
  • Check the base URL to ensure it points to the correct GitLab instance.
  • Common error messages may include 401 Unauthorized (authentication issues), 404 Not Found (incorrect project ID or package name), and 400 Bad Request (invalid request body). Resolving these involves correcting credentials, parameters, or request payload.

Links

Discussion