gitlab api proInstall

Summary

Update an existing GitLab release by specifying its tag name and modifying its name, description, and optionally its assets links in JSON format.

Inputs

• Authentication — Choose between using saved credentials or providing a custom GitLab server URL and access token.
• GitLab Server — Custom GitLab instance base URL, required only if using custom authentication.
• Access Token — Personal access token with API permissions, required only if using custom authentication.
• Project Locator — Method to identify the project either by ID or by path (owner and project name). Defaults to 'id'.
• Project ID — Numeric project ID used when Project Locator is set to 'id'.
• Project Owner — Namespace or owner of the project, used when Project Locator is set to 'path'.
• Project Name — Project slug or name, used when Project Locator is set to 'path'.
• Tag Name (required) — The tag name of the release to update.
• Name (required) — The new name for the release.
• Description — Optional new description for the release.
• Assets — Optional JSON string specifying assets links associated with the release.

Output shape

a single record representing the updated release object returned by the GitLab API

The operation requires a valid project identification (either by ID or path) and the tag name of the release. If assets JSON is provided, it must be a valid JSON string. The response includes all release data after update as returned by GitLab's API.

Examples

Example 1: Update a release using project ID

Set Project Locator to 'ID', provide Project ID, Tag Name, Name, and optionally Description and Assets JSON.

Example 2: Update a release using project path

Set Project Locator to 'Path', provide Project Owner and Project Name, Tag Name, Name, and optionally Description and Assets JSON.

Links

• n8n community nodes installation guide