Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.vers.sh/llms.txt

Use this file to discover all available pages before exploring further.

​
vers repo tag update

Atomically move a tag to a new commit, or change its description. No VMs are touched by this operation; it’s a metadata-only pointer update.

​
Synopsis

vers repo tag update <repo-name> <tag-name> --commit <new-commit-id>
vers repo tag update <repo-name> <tag-name> --description "new text"
vers repo tag update <repo-name> <tag-name> --commit <id> --description "text"

​
Description

Updates a tag in place. You must supply at least one of --commit or --description. The most common use is advancing a rolling tag like latest to point at a new build: 
vers commit              # → new commit c9e4…
vers repo tag update my-app latest --commit c9e4…
# ✓ Tag 'latest' in 'my-app' updated
The previous commit is not deleted; it’s simply no longer named by this tag. If you had other tags pointing at it, they’re unaffected.
The new commit must be owned by your org, same rule as vers repo tag create.

​
Options

OptionDescription
--commitMove the tag to this commit ID
--description, -dNew description for the tag

​
Examples

​
Rolling latest forward after a new build

vers commit
# ✓ Commit c9e4… created

vers repo tag update my-app latest --commit c9e4…

​
Rolling back

# Your team's latest is broken; pin it to the previous known-good commit.
OLD=$(vers repo tag get my-app known-good --format json | jq -r .commit_id)
vers repo tag update my-app latest --commit "$OLD"

​
Editing the description

vers repo tag update my-app known-good -d "2026-04-17 release candidate"

​
Both at once

vers repo tag update my-app staging --commit c9e4… -d "Rebuilt after migration 0042"

​
Error Cases

​
Repository or tag not found

vers repo tag update ghost latest --commit c9e4…
# Error: Repository, tag, or commit not found

​
Commit not found or forbidden

vers repo tag update my-app latest --commit 00000000-…
# Error: commit not found
# or: forbidden   (commit exists in another org)

​
Nothing to update

vers repo tag update my-app latest
# Error: at least one of --commit or --description must be provided

​
Notes

The CLI currently cannot clear a description (send null). The underlying API supports it via PATCH with an explicit null field, but the current vers repo tag update flags only let you overwrite with a new string or skip the field entirely.

​
See Also