wai-quantum 0.8.0, wai-quantum-qpu 0.4.0, wai-quantum-cli 0.2.3, the job service 0.2.1, and the Python and JavaScript packages 0.1.1 #564

Merged

dcharlot merged 4 commits from wai/quantum-release-0.8.0 into main 2026-11-01 22:15:41 -05:00

Conversation 0 Commits 4 Files changed 44 +277 -224

2026-11-01

Transaction Science

wai-quantum release 0.8.0: CI again, now the arm64 runner has disk ...

The previous run's jobs on linux-arm64 failed at checkout: the runner's host
had no space left. Nothing in the tree changes.

Co-Authored-By: Claude Opus 5.5 <[email protected]>

43e257541a

• View at this point in history

2026-11-01 20:40:54 -05:00

Transaction Science

wai-quantum release 0.8.0: the requirement the engine's README shows ...

The README and its zh-CN translation show `wai-quantum = "0.8"`, the
requirement that takes the crate at 0.8.0, which the docs check holds them to.

Co-Authored-By: Claude Opus 5.5 <[email protected]>

ab3bc1d4f0

• View at this point in history

2026-11-01 18:38:20 -05:00

Transaction Science

wai-quantum release 0.8.0: the wheel the Python README names, and the views page's sources ...

The Python README and its zh-CN translation name the wheel at 0.1.1, the
version the docs check holds them to. The views manifest records the new
digest of wai-quantum-views's lockfile, which the release moved: rebuilt with
wai/wai-quantum-views/build.sh in catthehacker/ubuntu:act-22.04 with Rust
1.98.0, as the views workflow rebuilds it. The page's bytes are unchanged.

Co-Authored-By: Claude Opus 5.5 <[email protected]>

fbcdbe795d

• View at this point in history

2026-11-01 12:00:27 -05:00

Transaction Science

wai-quantum 0.8.0, wai-quantum-qpu 0.4.0, wai-quantum-cli 0.2.3, the job service 0.2.1 and the Python and JavaScript packages 0.1.1: the release's versions, its changelog heading, and every lock ...

The engine moves to its next 0.y, a major bump before 1.0 (VERSIONING.md):
two of the entries it carries change engine::schema::FILES, a public array
whose length is part of its type. wai-quantum-qpu, whose functions take the
engine's types, moves with it to 0.4.0. The command line, the job service,
the Python package and the JavaScript package only gain, so each moves its
last number. Every dependent's requirement names the new versions, both
server.json files and the JavaScript README follow, and the seventeen
lockfiles that resolve any of them move with them, each read with --locked.
The desktop app stays 0.1.0. cargo-semver-checks keeps its baselines at the
versions last published.

The engine's version is among the sealed bytes of a stamped result, so the
page's pinned digests move (the course check's 969b2c1c... to 1a9aa0ad...,
the compile's ac948133... to beffb3cb..., the estimate's 8715e76b... to
db90b147...), the answer set's stored seal is written again
(WAI_ANSWER_BUNDLE_WRITE=1), and the notebooks' stored outputs are stored
again. The job pins strip the engine and schema and do not move.

Co-Authored-By: Claude Opus 5.5 <[email protected]>

3c4b10a261

• View at this point in history

2026-11-01 09:15:14 -05:00