Skip to main content

atmos version track update

Advance dependency versions to the newest releases allowed by your update policies and record them in the lock file. Use it to keep dependencies current while respecting version limits, cooldown windows, exclusions, and prerelease rules.

Unlike lock, update starts from the locked state and respects strategy caps, cooldown windows, include/exclude rules, and prerelease policy. Newer candidates held back by policy are reported with a reason.

Usage​

atmos version track update [track] [flags]

Flags​

--group
Limit the update to entries in the named version group.
--only
Limit the update to the named entries. Repeat the flag for multiple entries.
--format string
Output format: table, json, yaml, csv, tsv (default: table)

Examples​

# Update every entry in the default track within policy
atmos version track update

# Update only the infrastructure group in prod
atmos version track update prod --group=infrastructure

# Update two specific entries
atmos version track update prod --only=checkout --only=nginx

Example Output​

In an interactive terminal, --format=table (the default) renders a styled table. Use --format=csv or --format=tsv for delimited output; piped table output remains a table.

> atmos version track update --format=csv
Track,Name,From,To,Updated,Reason
prod,checkout,v6.1.0,v6.2.0,true,
prod,nginx,1.29.0,,false,"1.30.0 released 3d ago; cooldown 14d has not elapsed"

Use --format=yaml or --format=json for the full-fidelity result, including fields the table omits (e.g. digests):

track: prod
results:
  - name: checkout
    from: v6.1.0
    to: v6.2.0
    updated: true
  - name: nginx
    from: 1.29.0
    updated: false
    reason: "1.30.0 released 3d ago; cooldown 14d has not elapsed"