wai-quantum 0.8.1, wai-quantum-qpu 0.4.1, wai-quantum-cli 0.2.4, the job service 0.2.2 and the Python package 0.1.2 #619

Merged

dcharlot merged 1 commit from wai/quantum-release-0.8.1 into main 2026-11-04 19:25:16 -05:00

Conversation 0 Commits 1 Files changed 41 +266 -222

2026-11-04

Transaction Science

wai-quantum 0.8.1, wai-quantum-qpu 0.4.1, wai-quantum-cli 0.2.4, the job service 0.2.2 and the Python package 0.1.2: the release's versions, its changelog heading, and every lock ...

Every change since 0.8.0 only adds or fixes, so each package moves its last
number (VERSIONING.md, "Before 1.0"). cargo-semver-checks 0.51.0 finds no
semver update required for wai-quantum, wai-quantum-cli or wai-quantum-qpu
against 0.8.0, 0.2.3 and 0.4.0 on crates.io, and keeps its baselines at the
versions last published. Every dependent's requirement names the new
versions, both server.json files follow, and the seventeen lockfiles that
resolve any of them move with them, each read with --locked. The JavaScript
package stays 0.1.1, as nothing in it changed, and the desktop app stays
0.1.2; its requirements move with the others. VERSIONING.md's "Version
today" table already reads 0.8.x, 0.4.x and 0.2.x, so only its example of a
result's engine moves. The Python README and its zh-CN translation name the
wheel at 0.1.2, and the views manifest records the new digest of
wai-quantum-views's lockfile, the two things 0.8.0 needed after its release
commit. The page is rebuilt with wai/wai-quantum-views/build.sh on the build
host with Rust 1.99.1 (build-views.mjs --check passes): its script and styles
are unchanged, and the engine inside it is the engine as it is now, which
changed its bytes, not its size.

The engine's version is among the sealed bytes of a stamped result, so the
page's pinned digests move (the course check's 1a9aa0ad... to 49a9fdb8...,
the compile's beffb3cb... to 198ea9bd..., the estimate's db90b147... to
acbd7208...), the answer set's stored seal is written again
(WAI_ANSWER_BUNDLE_WRITE=1), and the notebooks' stored outputs are stored
again (ci/check.sh --write-notebooks). The job pins strip the engine and
schema and do not move.

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

a274776b50

• View at this point in history

2026-11-04 15:46:22 -05:00