GitLab · Create a release — A release for a tag, with notes — makes a release in a project, shown on its Releases page.

Who can do this

Workspace Admins and Editors, on every plan. Viewers see the step's settings but cannot change them.

Before you start

A GitLab connection with the api scope, whose user is a Developer or above in the project — see Connect GitLab.

Steps

  1. Select + where the step should go. In the step picker, open Apps, select GitLab, then Create a release. Or search GitLab.
  2. In Connection, choose your GitLab connection.
  3. In Project, choose the project — for example consulace/billing-service.
  4. In Tag, the tag — v1.4.0.
  5. Optional: in Name, the release's title.
  6. Optional: in Notes, what changed — GitLab's Markdown works.
  7. In From branch, choose a branch if the tag does not exist yet — Only when the tag does not exist yet: GitLab makes it from this branch. Leave it empty for an existing tag.
  8. Select Run this step to try it. This makes a real release.

Output

Field What it is
tag The release's tag — v1.4.0.
name Its name.
url The release's page in GitLab.

Good to know

  • A tag can have only one release. Creating a second release for the same tag fails.
  • A new tag needs From branch. Without it, GitLab cannot tell where to make the tag.
  • Each item runs the step once.

If something goes wrong

What you see Why What to do
GitLab refused: Ref is not specified. The tag does not exist and From branch is empty. Choose a branch in From branch, or create the tag first.
GitLab refused: Release already exists. The tag has a release already. Use a new tag.
Tag is empty when the step ran — an earlier step may not have given the value it names. The tag came out empty. Check the values it reads.
GitLab refused: 403 Forbidden. Check the connection's details on Connections. The token's user cannot create releases in the project — or the tag is protected. Give the user the Developer role or above, or Maintainer for a protected tag.