flog bump
Plan coherent workspace release versions and repair explicit workspace ranges.
Usage#
flog bump [options]
Examples#
flog bump --dry-run
flog bump --json
flog bump --yes
Options and behaviour#
Flog compares public workspace versions with the requested registry tag, then
plans minimum transitive release versions and explicit range repairs.
--dry-run and --json are read-only; --yes confirms noninteractive application.
Applying atomically updates reviewed manifests and the synchronized lock. It
never installs, runs lifecycle scripts, creates artifacts, or mutates a registry.
An existing valid multi-target lock is transformed locally when only workspace
versions and workspace: ranges change. Unrelated registry snapshots, peer
contexts, platform selections, and integrity values are preserved.
If reuse cannot be proven safe, application reports and performs full resolution where possible, or fails closed for an invalid or incompatible lock. A dry run does not start that fallback: text and JSON report lock validation as pending.
Publication-baseline checks still read anonymous registry metadata. Human output reports the active baseline and lock phase. Baseline checks have a 30-second phase deadline; full fallback resolution has a two-minute deadline. Either fails with a clear timeout diagnostic instead of waiting indefinitely.
Run flog help bump for complete current help.