Expand description
Binary-driven instance upgrade.
The newer binary carries the newer payload, so an upgrade is mechanical: refuse atomically while any managed file is locally edited, reinstall from the embedded payload, prune what the new version stopped managing — inside the vendored directory only, and never through a symlink — and report the rule-ID diff the operator reconciles by hand. Copier’s model; what changed between versions is the changelog’s business.
Structs§
- Upgrade
Options - What an upgrade was asked to do.
- Upgrade
Outcome - What an upgrade did.
Functions§
- upgrade
- Upgrade an installed instance to this binary’s version.