Archive and checksum asset names for a tag and triple. Must match the
archive: pattern in .github/workflows/release.yml, which is
bbcloud-$tag-$target; cargo-binstall’s default templates key off the
crate name, which is why the prefix is bbcloud and not the binary name.
Decides who owns the binary at exe from its path alone. Overwriting a
package-manager-owned file would leave brew or cargo believing it manages
a file it no longer controls, so those cases delegate instead.
True only when both versions parse and latest is strictly greater. An
unparseable remote tag is never an upgrade, so a malformed API response
cannot trigger a download.
The command that upgrades an install of this kind. A standalone install is
the only one bb can replace itself, so it is the only one pointed back at
bb update; the package-manager cases must go through their own manager or
brew and cargo would keep believing they manage a file they no longer wrote.