GitLab Release CLI tool

The release-cli is in maintenance mode.

The release-cli does not accept new features. All new feature development happens in the glab CLI, so you should use the glab CLI whenever possible. You can use the feedback issue to share any comments.

Switch from `release-cli` to `glab` CLI

For API usage details, see the glab CLI project documentation.
With a CI/CD job and the release keyword, change the job’s image to use the cli:latest image. For example:

release_job:
  stage: release
  image: registry.gitlab.com/gitlab-org/cli:latest
  rules:
    - if: $CI_COMMIT_TAG
  script:
    - echo "Running the release job."
  release:
    tag_name: $CI_COMMIT_TAG
    name: 'Release $CI_COMMIT_TAG'
    description: 'Release created using the cli.'

Fall back to `release-cli`

History

The availability of this feature is controlled by a feature flag. For more information, see the history.

CI/CD jobs that use the release keyword use a script that falls back to using release-cli if the required glab version is not available on the runner. The fallback logic is a safe-guard to ensure that projects that have not yet migrated to use glab CLI can continue working.

This fallback is scheduled to be removed in GitLab 19.0 with the removal of release-cli.

Docs

Edit this page to fix an error or add an improvement in a merge request.

Create an issue to suggest an improvement to this page.

Product

Create an issue if there's something you don't like about this feature.

Propose functionality by submitting a feature request.

Feature availability and product trials

View pricing to see all GitLab tiers and features, or to upgrade.

Try GitLab for free with access to all features for 30 days.

Get help

If you didn't find what you were looking for, search the docs.

If you want help with something specific and could use community support, post on the GitLab forum.

For problems setting up or using this feature (depending on your GitLab subscription).

Request support