Repository navigation
Releases: addisdev/fleet-runner
Release list
v0.9.2 — a reserved phone is lent to no one else
Install
macOS and Linux:
curl -fsSL https://raw.githubusercontent.com/addisdev/fleet-runner/main/install.sh | sh
Windows:
irm https://raw.githubusercontent.com/addisdev/fleet-runner/main/install.ps1 | iex
Both require Node 22.13 or newer on PATH -- these archives do not
carry a runtime -- and both verify their download against
SHASUMS256.txt below and refuse to install if it does not match.
Then fleet up. fleet doctor says what the machine can and cannot
run, and why.
Every archive carries the same program -- the bundle is JavaScript,
and only the launcher differs. They are named per platform because the
install scripts build the URL before they know that.
Nothing here is code-signed. macOS will quarantine an archive
downloaded in a browser; the install script is not affected.
See CHANGELOG.md.
v0.9.1 — a sleeping phone is woken, a locked one says so
Install
macOS and Linux:
curl -fsSL https://raw.githubusercontent.com/addisdev/fleet-runner/main/install.sh | sh
Windows:
irm https://raw.githubusercontent.com/addisdev/fleet-runner/main/install.ps1 | iex
Both require Node 22.13 or newer on PATH -- these archives do not
carry a runtime -- and both verify their download against
SHASUMS256.txt below and refuse to install if it does not match.
Then fleet up. fleet doctor says what the machine can and cannot
run, and why.
Every archive carries the same program -- the bundle is JavaScript,
and only the launcher differs. They are named per platform because the
install scripts build the URL before they know that.
Nothing here is code-signed. macOS will quarantine an archive
downloaded in a browser; the install script is not affected.
See CHANGELOG.md.
v0.9.0 — green you can believe
Install
macOS and Linux:
curl -fsSL https://raw.githubusercontent.com/addisdev/fleet-runner/main/install.sh | sh
Windows:
irm https://raw.githubusercontent.com/addisdev/fleet-runner/main/install.ps1 | iex
Both require Node 22.13 or newer on PATH -- these archives do not
carry a runtime -- and both verify their download against
SHASUMS256.txt below and refuse to install if it does not match.
Then fleet up. fleet doctor says what the machine can and cannot
run, and why.
Every archive carries the same program -- the bundle is JavaScript,
and only the launcher differs. They are named per platform because the
install scripts build the URL before they know that.
Nothing here is code-signed. macOS will quarantine an archive
downloaded in a browser; the install script is not affected.
See CHANGELOG.md.
v0.8.0
Install
macOS and Linux:
curl -fsSL https://raw.githubusercontent.com/addisdev/fleet-runner/main/install.sh | sh
Windows:
irm https://raw.githubusercontent.com/addisdev/fleet-runner/main/install.ps1 | iex
Both require Node 22.13 or newer on PATH -- these archives do not
carry a runtime -- and both verify their download against
SHASUMS256.txt below and refuse to install if it does not match.
Then fleet up. fleet doctor says what the machine can and cannot
run, and why.
Every archive carries the same program -- the bundle is JavaScript,
and only the launcher differs. They are named per platform because the
install scripts build the URL before they know that.
Nothing here is code-signed. macOS will quarantine an archive
downloaded in a browser; the install script is not affected.
See CHANGELOG.md.
v0.7.2
Install
macOS and Linux:
curl -fsSL https://raw.githubusercontent.com/addisdev/fleet-runner/main/install.sh | sh
Windows:
irm https://raw.githubusercontent.com/addisdev/fleet-runner/main/install.ps1 | iex
Both require Node 22.13 or newer on PATH -- these archives do not
carry a runtime -- and both verify their download against
SHASUMS256.txt below and refuse to install if it does not match.
Then fleet up. fleet doctor says what the machine can and cannot
run, and why.
Every archive carries the same program -- the bundle is JavaScript,
and only the launcher differs. They are named per platform because the
install scripts build the URL before they know that.
Nothing here is code-signed. macOS will quarantine an archive
downloaded in a browser; the install script is not affected.
See CHANGELOG.md.
v0.7.1
Install
macOS and Linux:
curl -fsSL https://raw.githubusercontent.com/addisdev/fleet-runner/main/install.sh | sh
Windows:
irm https://raw.githubusercontent.com/addisdev/fleet-runner/main/install.ps1 | iex
Both require Node 22.13 or newer on PATH -- these archives do not
carry a runtime -- and both verify their download against
SHASUMS256.txt below and refuse to install if it does not match.
Then fleet up. fleet doctor says what the machine can and cannot
run, and why.
Every archive carries the same program -- the bundle is JavaScript,
and only the launcher differs. They are named per platform because the
install scripts build the URL before they know that.
Nothing here is code-signed. macOS will quarantine an archive
downloaded in a browser; the install script is not affected.
See CHANGELOG.md.
v0.7.0
Install
macOS and Linux:
curl -fsSL https://raw.githubusercontent.com/addisdev/fleet-runner/main/install.sh | sh
Windows:
irm https://raw.githubusercontent.com/addisdev/fleet-runner/main/install.ps1 | iex
Both require Node 22.13 or newer on PATH -- these archives do not
carry a runtime -- and both verify their download against
SHASUMS256.txt below and refuse to install if it does not match.
Then fleet up. fleet doctor says what the machine can and cannot
run, and why.
Every archive carries the same program -- the bundle is JavaScript,
and only the launcher differs. They are named per platform because the
install scripts build the URL before they know that.
Nothing here is code-signed. macOS will quarantine an archive
downloaded in a browser; the install script is not affected.
See CHANGELOG.md.
v0.6.2
Install
macOS and Linux:
curl -fsSL https://raw.githubusercontent.com/addisdev/fleet-runner/main/install.sh | sh
Windows:
irm https://raw.githubusercontent.com/addisdev/fleet-runner/main/install.ps1 | iex
Both require Node 22.13 or newer on PATH -- these archives do not
carry a runtime -- and both verify their download against
SHASUMS256.txt below and refuse to install if it does not match.
Then fleet up. fleet doctor says what the machine can and cannot
run, and why.
Every archive carries the same program -- the bundle is JavaScript,
and only the launcher differs. They are named per platform because the
install scripts build the URL before they know that.
Nothing here is code-signed. macOS will quarantine an archive
downloaded in a browser; the install script is not affected.
See CHANGELOG.md.
v0.6.1
Install
macOS and Linux:
curl -fsSL https://raw.githubusercontent.com/addisdev/fleet-runner/main/install.sh | sh
Windows:
irm https://raw.githubusercontent.com/addisdev/fleet-runner/main/install.ps1 | iex
Both require Node 22.13 or newer on PATH -- these archives do not
carry a runtime -- and both verify their download against
SHASUMS256.txt below and refuse to install if it does not match.
Then fleet up. fleet doctor says what the machine can and cannot
run, and why.
Every archive carries the same program -- the bundle is JavaScript,
and only the launcher differs. They are named per platform because the
install scripts build the URL before they know that.
Nothing here is code-signed. macOS will quarantine an archive
downloaded in a browser; the install script is not affected.
See CHANGELOG.md.
v0.6.0
Install
macOS and Linux:
curl -fsSL https://raw.githubusercontent.com/addisdev/fleet-runner/main/install.sh | sh
Windows:
irm https://raw.githubusercontent.com/addisdev/fleet-runner/main/install.ps1 | iex
Both require Node 22.13 or newer on PATH -- these archives do not
carry a runtime -- and both verify their download against
SHASUMS256.txt below and refuse to install if it does not match.
Then fleet up. fleet doctor says what the machine can and cannot
run, and why.
Every archive carries the same program -- the bundle is JavaScript,
and only the launcher differs. They are named per platform because the
install scripts build the URL before they know that.
Nothing here is code-signed. macOS will quarantine an archive
downloaded in a browser; the install script is not affected.
See CHANGELOG.md.