Skip to content

Building a release tells you when it cannot

Choose a tag to compare

View all tags
@github-actions github-actions released this 26 Aug 13:44
· 9 commits to main since this release
v1.22.0
d199d52
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Bug fixes

  • Building the installers locally failed with an unreadable error. On a machine whose Node came from Homebrew, npm run build:installers died with a bare stack trace and no message. The underlying reason is that Homebrew builds Node against shared libraries, which makes it unable to produce a single-file executable and, more importantly, unable to produce one that would run on anyone else's machine.

    The build now checks for both problems before it starts, uses an official Node automatically if one is installed (fnm, nvm, volta, asdf, or /usr/local/bin), and otherwise stops with an explanation and the fix. It also says outright that the Node version is not the problem, because "update Node" is the natural conclusion and the wrong one.

Published releases were never affected: CI has always built them with official Node.

Install

Download the installer for your platform below. Nothing else needed, not even Node.

Prefer npm? Install from the tarballs attached below: npm install -g hypergate-shell-<os>-<arch>-1.22.0.tgz hypergated-1.22.0.tgz. (hypergated is not on the public registry yet. These are the same packages, and they are what the in-app updater installs.)

Bare hypergate command-line binaries are attached too, and SHA256SUMS is signed with the GPG key at docs/release-signing-key.asc, so you can verify what you downloaded.

Assets 35
Loading