Reference
Update
Keep bay current with bay update, a daily background check, release channels, and version pins.
bay is in development. These pages describe bay as it will ship.
bay update installs a newer bay release. It verifies the signed SHA256SUMS, the signed VERSION, and the sha256 before it replaces the binary. It swaps the binary in one rename, so a running command keeps working. It refuses a downgrade unless --version or a pin asks for it. Like every command, it prints one bay.result/1 document.
bay update # the newest release on your channel
bay update --channel latest # switch to the latest channel
bay update --version 0.1.0 # one exact versionAutomatic updates
bay checks for a new release at most once a day. The check runs in the background and never blocks a command. Set BAY_DISABLE_AUTOUPDATE=1 to turn it off on one machine. Set auto = false in the [update] table to turn it off for a repository.
[update]
auto = falseChannels
stable follows the latest release, and it is the default. latest follows the newest pre-release. Set the channel with --channel, or with channel in the [update] table.
Pins
A pin limits the versions that bay can run. Write an exact version, such as =0.1.0, or a range. A pin is a requirement, not a hint. bay update refuses a version outside the pin. bay doctor goes red when the installed version is outside the pin.
[update]
version = "=0.1.0"Refusals
| Code | Meaning | What to do next |
|---|---|---|
UPDATE_UNVERIFIED | The signature of SHA256SUMS or the sha256 of the archive did not verify. | Keep the current binary. Retry later, and report it if it repeats. |
UPDATE_PINNED | The version you asked for is outside the pin. | Pick a version inside the pin, or change the pin. |
UPDATE_UNAVAILABLE | No release could be read: the network or the release repository is not reachable, or no release matches the channel or version. | Retry later. This refusal is transient. |