blowhorn upgrade
Carry this Mac's local data from an earlier home into this one.
blowhorn upgrade
Carry this Mac's local data from an earlier home into this one. It carries profiles, analytics history, every run-ledger line (duplicates included), the write-back spool, the pause and the settings you changed. The earlier home is left exactly as it was, nothing already in the new home is overwritten, and a file that differs is kept and named in the report. Browser session folders are never carried. The pause is carried first, so a paused Mac is paused in the new home even if a later part fails. Each completed carry is recorded in upgrades.json in the new home, so it runs once; a carry that fails is not recorded and the next run tries again, adding nothing twice. While a scheduled pass is still running from the earlier home the answer is busy and nothing is touched. The earlier home is found from --source, then from the engine record the app wrote before this launch, then from the previous checkout at ~/code/blowhorn. A folder that belongs to another macOS user is never carried, even when named with --source; the report says so and carries nothing. --dry-run -- including one that comes from your settings -- only plans: the answer is planned, nothing is written, and the upgrade is still due. The desktop app runs this itself at launch; you never need a terminal for it.
blowhorn upgrade [OPTIONS]| Flag | Type | Default | Description |
|---|---|---|---|
--source |
string | The earlier version's home to carry data from; without it the engine record from before this launch is read, then the previous checkout at ~/code/blowhorn | |
--json |
boolean | false |
Emit the report as one JSON object: ok, status (upgraded, planned, current, busy or failed), dry_run, target, source, a one-line summary, and one entry per step with its counts and any files kept |
--platform |
string | Accepted and ignored by blowhorn upgrade: this command never acts on a platform, so --platform has no effect here -- including a value inherited from BLOWHORN_PLATFORM or defaults.platform in .blowhorn.yaml |
|
--pace |
string | Accepted by blowhorn upgrade because --pace is a global flag, but this command does no paced work -- it sleeps between nothing -- so the value changes nothing about how it runs and appears only in the Pace column of the -v summary. Resolved as CLI flag, then BLOWHORN_PACE, then defaults.pace in .blowhorn.yaml (normal when none is set); an unrecognized value is rejected before anything runs |
|
--risk-profile |
string | Accepted by blowhorn upgrade because --risk-profile is a global flag, but this command does no gated work -- no Risk Profile hold, cap or pace applies to it -- so the value changes nothing about how it runs. A value after the command word wins over one before it; an unrecognized value is rejected before anything runs |
Also takes the shared flags: --config, --log-dir, --profile, --exclude, --headless, --chrome-launch, --headed, --dry-run, --verbose.
Examples:
blowhorn upgrade
blowhorn upgrade --dry-run
blowhorn upgrade --dry-run --json
blowhorn upgrade --source ~/code/blowhorn-oldOutput: json with --json, text otherwise.