Skip to main content
Version: 0.15 (glpkg CLI)

glpkg registry

Query the GitLab package registry and delete published versions.

glpkg registry <command>
CommandDescription
versions <package>List all published versions, newest first
delete <package> <version>Delete one published version (irreversible)
info|view <package>Show package information, like npm view
list|lsList packages in a group
search|s <query>Search packages by name in a group

versions​

glpkg registry versions @your-org/utils --group your-org
glpkg registry versions @your-org/utils --json
OptionDescription
-g, --group <group>GitLab group (path or ID). Default: the group recorded in glpkg.lock.json
--jsonJSON output

Requires a token. Without --group and without a lock entry, it fails:

✗ No GitLab group known for @your-org/utils
→ Pass --group <group>, or record it in glpkg.lock.json: glpkg lock set <pkg> --group <group>

delete​

glpkg registry delete @your-org/utils 1.2.4-dev.1720000000000 --group your-org --dry-run
glpkg registry delete @your-org/utils 1.2.4-dev.1720000000000 --group your-org
OptionDescription
-g, --group <group>GitLab group (default: from glpkg.lock.json)
--dry-runShow what would be deleted
-y, --yesSkip the confirmation prompt
--jsonJSON output

Requires a token with the api scope and permission to delete packages in the project.

info​

glpkg registry info @your-org/utils
glpkg registry info @your-org/utils --version 1.2.3 --json
OptionDescription
-v, --version <version>A specific version
--source <type>project, group or both (default both)
--jsonJSON output

info takes the group and project from glpkg.lock.json; it has no --group option.

glpkg registry list --group your-org
glpkg registry search utils --group your-org --json

--group is required for both.

note

info, list and search use the token saved with glpkg config save and always query gitlab.com.