Warning

The product is in closed beta and not open to the public.

check-update-file

vb check-update-file [OPTIONS] [VERSION]

Description

Print a JSON list of candidate paths affected by the difference between the current check-out version and VERSION. VERSION is selected using the same rules as update, including current and latest. Run pull first if remote changes should be included. This command does not sync, scan working files, refresh vfile signatures, or compute merges. It compares complete manifests, including delta-manifest baselines.

Output contains schemaVersion (1), from and target (full check-in UUIDs), and files (an array of objects with path and reason). Paths are relative to the workspace root and sorted by their UTF-8 byte representation. Reasons are added-in-target, removed-in-target, content-changed, metadata-changed, or content-and-metadata-changed. A rename is represented by removal of the old path and addition of the new path, including changes in filename case. Unchanged paths are omitted.

This is a version comparison, not an exact update write plan. Local renames, missing working files, unmanaged files, and merge conflicts are not inspected. Editors must account for those separately. After preparing affected resources, run vb update --nosync TARGET using the returned target UUID. The caller must keep the workspace stable between commands.

On success, stdout contains only JSON. Errors use stderr and a nonzero exit status; no partial JSON is emitted.

Options

--latest

Acceptable in place of VERSION latest

See Also

See also

pull, update