floe version
floe binary, Floe’s CLI, a link to the
documentation, and an update hint when a newer release is available.
Output
Output
Output
v: the first reads like floe 1.12.0. In floe 1.11.0 and
earlier the hint named the release by its tag instead, as in
Update available: v1.x.x run `floe update` to upgrade.
The update check
floe version is the only command that checks for a newer release on its own. send and
receive never do, and floe update checks only when you run it. The check asks GitHub for the
latest release tag (https://api.github.com/repos/jannskiee/floe/releases/latest) and keeps the
answer for 24 hours in floe/update-check.json, inside your user config folder:
While a kept answer is less than 24 hours old,
floe version asks GitHub nothing, so the hint can
appear up to a day after a release comes out. Delete that file to force a fresh check.
floe update --check also asks GitHub on a script or manual install, but it leaves the kept answer
as it is, and on a package-managed install it stops before asking. With no fresh answer kept,
floe version waits at most 1 second for GitHub and prints no hint if the answer is slower, so it
never stalls on a slow network.
The hint names both ways to update because on an install that a
package manager owns, floe update installs nothing and names the
package manager’s upgrade command instead: see
Update the CLI.
In floe 1.12 and later the hint ignores a release whose tag is not exactly vX.Y.Z, whether the
name came from GitHub or from the kept answer. floe update stops on such a name too: see
Messages.
Set FLOE_NO_UPDATE_CHECK=1 to skip the check and the hint entirely. Binaries built from
source report floe dev and never check.
Alternatives
You can also use the root flag:Terminal
floe version (for example
floe 1.x.x). No docs link, no update hint, and no request to GitHub.