Skip to content

0.8.0-pre.2

Pre-release
Pre-release

Choose a tag to compare

@unforcedagi unforcedagi released this 31 Oct 00:07
74ae62d

The second prerelease of Parachute v0.8, the test build for Prism's Nov 9 handoff. The npm package is
@openparachute/core and the command is parachute.

Since 0.8.0-pre.1 (none of it touches the embedded contract; Benjamin's suite passes unchanged):

  • Wikilinks longer than 48 bytes resolve on Durable Objects (#23).
  • Import resolves wikilinks once from a title index and commits in chunks (#25).
  • Tag queries over 100+ child tags, path_prefix and rename-tag stay under Durable Object SQLite's caps (#27, #28).
  • A rename's cascade writes reach live subscribers (#29).
  • Restoring an old snapshot keeps its metadata exact (#32).
  • OAuth refresh ignores a resource it can't match (as 0.7.6 did); /oauth/token answers a non-form body 400 and logs it (#22, #31).
  • Takeover reads the old units' environment as systemd does (#13, #20, #30).
  • The darwin-arm64 bundle is built on macos-15 (GitHub retires macos-14 on Nov 2) (#33).

Built by CI from this tag's commit, never on a laptop:

  • parachute-core-0.8.0-pre.2-darwin-arm64.tar.gz, signed ad hoc with the hardened runtime (runtime/bun with
    allow-jit only). It is the tree that embedded/bundle and Benjamin's compatibility suite passed on, on macos-15.
  • parachute-core-0.8.0-pre.2-linux-x64.tar.gz, the tree every contract suite ran on.
  • SHA256SUMS for both tarballs: shasum -a 256 -c SHA256SUMS (Linux: sha256sum -c SHA256SUMS).
  • openparachute-core-0.8.0-pre.2.tgz and npm-SHA256SUMS: the npm package, tested by CI with npm i -g and
    bun add -g, with Benjamin's suite run on the npm install. It is not on npm yet: the CI publish was refused (404) because the package has no trusted publisher
    set on npmjs.com (RELEASING.md, one-time setup step 3). Until it is, npm's next stays at 0.8.0-pre.1. This file is
    byte-identical to the one the release workflow tested and will publish (its sha256 is in npm-SHA256SUMS).

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.

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.