Emscripten builds of the Hyperion compiler, served at
https://binaries.theqrl.org/bin/. @theqrl/hypc
downloads its compiler from here and checks it against bin/list.json.
bin/list.jsonis generated from the files inbin/. Never edit it by hand.- A binary, once added, is never modified, renamed or deleted. A bad release burns its version number; publish a new one.
- Every binary must be the
hypjson.jsasset of the matchingtheQRL/hyperionGitHub release: identical sha256 to that release'sSHA256SUMS, and a build provenance attestation that verifies. Versions that predate those release artefacts are listed inscripts/release-policy.json; nothing new may be added there.
CI (.github/workflows/verify.yml) enforces all three on every pull request and push to main.
Requires Node.js 22+ and the GitHub CLI (gh) 2.102.0 or later, signed in. Both scripts refuse an
older gh: versions 2.51.0 to 2.101.0 accept an attestation from any workflow whose path begins with
the pinned one (GHSA-wjmr-j3rp-mh2g).
npm ci --ignore-scripts --prefix scripts
node scripts/add-release.mjs 0.2.1 # download, verify sha256 + attestation, copy, regenerate list.json
node scripts/verify-list.mjs # same checks CI runs
node scripts/check-releases.mjsThen open a pull request with the new bin/hypjson-v<version>+commit.<hash>.js and the
regenerated bin/list.json.
# releases after 0.2.0; needs gh 2.102.0 or later (GHSA-wjmr-j3rp-mh2g)
gh attestation verify hypjson-v0.2.1+commit.<hash>.js --repo theQRL/hyperion \
--signer-workflow theQRL/hyperion/.github/workflows/ci.ymlor compare its sha256 with the hypjson.js line of the release's SHA256SUMS on
https://github.com/theQRL/hyperion/releases.