Argo CD Git tag path prefixes
Introduced 2026-08-04 · score 0.98
HOW TO USE IT
When resolving a Git semver target within a tag path, set `tagPrefix` with `targetRevision`. Argo CD filters tags by that prefix, strips it for constraint evaluation, then restores it on the resolved version; semver constraints match tags, not branches.
argocd app set <APPNAME> --revision '1.0.*' --tag-prefix 'component-b/'spec:
source:
targetRevision: 1.0.*
tagPrefix: component-b/WHY THIS HELPS
Resolve a semver target revision against tags scoped to a component or environment prefix.
REQUIREMENTS AND LIMITATIONS
- Version: v3.5.0
- APPNAME (required): Application name.
- --revision: Tracking source branch, tag, commit, or Helm chart version; use a semver constraint for Git tag resolution.
- --tag-prefix: Filters Git tags by this prefix before evaluating `targetRevision` as a semver constraint.
- targetRevision (required): For this task, the semver constraint used to resolve a Git tag; constraints match tags, never branches.
- tagPrefix: Filters tags to those with the prefix, strips it before comparing against `targetRevision`, and re-adds it to the resolved version. No mutually exclusive values are documented.
- Semver constraints are matched against tags, never branches.
- The source describes basic support for Git tag path prefixes.
FIRST-PARTY EVIDENCE
- https://github.com/argoproj/argo-cd/releases/tag/v3.5.0
- https://github.com/argoproj/argo-cd/pull/27290
- https://github.com/argoproj/argo-cd/blob/v3.5.0/docs/user-guide/commands/argocd_app_set.md
- https://github.com/argoproj/argo-cd/blob/v3.5.0/docs/user-guide/tracking_strategies.md
Check the installed version and the source before using it. Entry JSON