macOS
Homebrewverified · 100%
brew install gitlab-release-clilocal Homebrew formula metadata
brew
Install gitlab-release-cli with Homebrew, apk, Nix, scoop, pacman
Toolset to create, retrieve and update releases on GitLab. Version 0.24.0 via Homebrew; verified from local package data.
install
Additional install commands
Linux
Alpine Linux apkverified · 92%
sudo apk add gitlab-release-cliAlpine Linux edge package indexes · gitlab-release-cli · source: dl-cdn.alpinelinux.org
Nixverified · 92%
nix profile install nixpkgs#gitlab-release-clinixpkgs package indexes · pkgs/by-name/gi/gitlab-release-cli/package.nix · source: api.github.com
Arch Linux pacmanverified · 92%
sudo pacman -S release-cliArch Linux sync databases · release-cli · source: geo.mirror.pkgbuild.com
Windows
Scoopverified · 92%
scoop install main/gitlab-release-cliScoop official bucket manifest trees · bucket/gitlab-release-cli.json · source: api.github.com
overview
Package summary
Toolset to create, retrieve and update releases on GitLab
Project links
Commands and aliases
- release-cli
history
Project history and usage
GitLab Release CLI is a small Go command-line tool created by GitLab to bridge GitLab CI/CD jobs and the GitLab Releases API. Its role is narrower than a general release manager: it turns release metadata from CI jobs or command-line flags into GitLab Release objects.
Project history
The project was introduced with GitLab 12.10 and published as a separate GitLab-hosted repository in 2020. The repository documentation describes it as a decoupled utility that can be invoked by GitLab Runner, third-party CI systems, or directly from a shell.
GitLab's documentation later moved release automation toward the broader glab CLI. The Release CLI page marks the feature as deprecated in GitLab 18.0 and describes a migration path from release-cli to glab for CI/CD jobs using the release keyword.
Adoption history
Release CLI's adoption followed GitLab CI/CD rather than a broad stand-alone CLI community. It mattered most to teams that wanted release objects, changelog text, tag metadata, and asset links produced as part of a GitLab pipeline.
How it is used
Practitioners use release-cli inside jobs defined in .gitlab-ci.yml, often on tag pipelines, where CI-provided values such as CI_JOB_TOKEN and CI_PROJECT_ID authenticate the Releases API call. The tool can also create, read, and update releases from a terminal when supplied with an access token and project information.
Why package nerds care
For package maintainers, release-cli is an example of a vendor-specific CI helper that escaped the container image boundary and became a packaged binary in systems such as Homebrew. Its maintenance-mode status also shows the lifecycle risk of packaging a narrow integration tool after the vendor folds the workflow into a larger CLI.
Timeline
- 2020: Introduced with GitLab 12.10 and released as v0.1.0.
- 2025: v0.24.0 appeared in the project release stream.
- GitLab 18.0: GitLab documentation marked release-cli as deprecated in favor of glab.
Related projects
- GitLab Runner passes CI job context to release-cli when release jobs are executed.
- glab is the GitLab CLI named by GitLab documentation as the migration target for release workflows.
Sources
security posture
Risk level: green
narrow executable package without higher-risk signals.
Risk classifier
green risk · low confidence · appliance
Why
- narrow executable package without higher-risk signals
Signals
- metadata:no-higher-risk-signals
Install behavior
- No Homebrew post-install hook is recorded in formula metadata.
- Homebrew bottle metadata is available for 8 platform targets.
- Build metadata lists 1 build dependencies.
Recommended review
Before unattended agent use, check whether the tool reads plaintext credentials, writes remote state, publishes artifacts, or shells out to plugins.
local files
Configuration and credential file locations
These source-backed paths show where this package keeps local settings or durable credentials. Automic Vault can use them as review targets for secret scanning, migration, and command approval.
Configuration files
Config paths the tool may read or write during local use.
- Unix
.gitlab-ci.yml
executables
Installed executables
| Command | Kind | Exposure | Note |
|---|---|---|---|
release-cli | cli | global executable |
freshness
Version and freshness
These signals separate page generation age, package-manager activity, and upstream release comparison. Version lag is warned only when an evidence URL and comparable versions are present.
page generated2026-07-08
manager version0.24.0
manager updated
local dataok
upstreamnot checked
latest detectednot detected
https://gitlab.com/gitlab-org/release-cli
- infoNo package-manager update timestamp was available.low confidence
- infoRelease/tag comparison is only available for GitHub repositories.https://gitlab.com/gitlab-org/release-clinone confidence
install metadata
Package metadata
| Package key | brew:gitlab-release-cli |
|---|---|
| Version | 0.24.0 |
| Package manager | Homebrew |
| Package manager page | https://formulae.brew.sh/formula/gitlab-release-cli |
| Homepage | https://gitlab.com/gitlab-org/release-cli |
| Repository | https://gitlab.com/gitlab-org/release-cli |
| Upstream docs | https://docs.gitlab.com/user/project/releases/release_cli |
| License | MIT |
| Source archive | https://gitlab.com/gitlab-org/release-cli/-/archive/v0.24.0/release-cli-v0.24.0.tar.bz2 |
| Build dependencies | go |
| Bottle | available (on arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, arm64_ventura, sonoma, ventura, x86_64_linux) |
| Homebrew post-install | not defined |
| Service | none declared |
registry facts
Source database details
| Source Database | Homebrew formula API |
|---|---|
| Tap | homebrew/core |
| Full Name | gitlab-release-cli |
| Version Scheme | 0 |
| Revision | 0 |
| Head Version | HEAD |
| Bottle Stable Root URL | https://ghcr.io/v2/homebrew/core |
| Deprecated | no |
| Disabled | no |
| Keg Only | no |
| URL Keys |
|
source database matches
Other package-manager records
Matches are pulled from external package-manager indexes and kept separate from local Automic Vault package links.
Nix95%
gitlab-release-cli
nix profile install nixpkgs#gitlab-release-cli- normalized package name match
- Matched by: Gitlab Release Cli
apk95%
gitlab-release-cli 0.24.0-r10
GitLab Release command-line tool
https://gitlab.com/gitlab-org/release-cli
sudo apk add gitlab-release-cli- License: MIT
- Architecture: x86_64
- Source Package: gitlab-release-cli
- 1 dependencies
- 1 provides
- normalized package name match
- Matched by: Gitlab Release Cli
apk95%
gitlab-release-cli-doc 0.24.0-r10
GitLab Release command-line tool (documentation)
https://gitlab.com/gitlab-org/release-cli
sudo apk add gitlab-release-cli-doc- License: MIT
- Architecture: x86_64
- Source Package: gitlab-release-cli
- normalized package name match
- Matched by: Gitlab Release Cli
Scoop95%
main/gitlab-release-cli
scoop install main/gitlab-release-cli- normalized package name match
- Matched by: Gitlab Release Cli
pacman92%
release-cli 0.24.0-1
Gitlab Release CLI
https://gitlab.com/gitlab-org/release-cli
sudo pacman -S release-cli- License: MIT
- Architecture: x86_64
- 1 dependencies
- installed executable or alias match
- Matched by: Release Cli
source trail
Generated from repository data
This page is generated by av-web from the private package SQLite artifact built by scripts/generate-pkg-sqlite.py.
Combined YAML source
View the package source record on GitHub.
Used sources
- Geiger risk classifier
- Nucleus package database
- av.db category and tag curation
- cross-ecosystem install command graph
- curated configuration and credential file locations
- curated package history
- external package-manager database matches
- package relationship graph
- package version freshness
- package-page enrichment