Repository navigation
0.8.0-pre.1
Pre-releaseThe first prerelease of Parachute v0.8: the vault and the hub as one program. The npm package is
@openparachute/core and the command is parachute (parachute-core is the same program under another name).
Built by CI from this tag's commit, never on a laptop:
parachute-core-0.8.0-pre.1-darwin-arm64.tar.gz, signed ad hoc with the hardened runtime (runtime/bunwith
allow-jitonly). It is the tree thatembedded/bundleand Benjamin's compatibility suite passed on, on macos-14.parachute-core-0.8.0-pre.1-linux-x64.tar.gz, the tree every contract suite ran on.SHA256SUMSfor both tarballs:shasum -a 256 -c SHA256SUMS.openparachute-core-0.8.0-pre.1.tgzandnpm-SHA256SUMS: the npm package. It is tested by CI with
npm i -gandbun add -g, with Benjamin's suite run on the npm install. It is not on npm yet; the first
publish is done by hand (RELEASING.md).
Run it: unpack, then bin/parachute --help. For a host application: bin/parachute bootstrap --embedded --json,
then bin/parachute serve --embedded --home <dir> --listen 127.0.0.1:<port> --vault-listen 127.0.0.1:<port>.
See docs/PRISM.md.
To install it for yourself: bin/parachute install, which links parachute and parachute-core into
~/.local/share/parachute-core/bin. On a machine with Parachute 0.7 it leaves the old parachute alone and tells
you to use parachute-core. Read the README's "Install" section before using bun add -g there.
On a machine with 0.7: parachute-core takeover (with --dry-run first) moves the home the old hub and vault
keep onto v0.8, keeps the old programs installed but off, and parachute-core takeover --rollback goes back. This is
a prerelease: back up a home you care about first.