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

dcharlot commented 2026-11-01 09:15:18 -05:00

Owner

Copy link

The quantum packages' next release, as one change: versions, the changelog's release heading, every lockfile, and the pins that move with the engine's version. Once it merges, the crates are published, the command line is tagged (which builds its binaries, the Python wheels and the npm tarball), and the job service and the site are deployed from the merged commit.

Versions

Package	Was	Now	Why
wai-quantum	0.7.0	0.8.0	Two entries this release carries change engine::schema::FILES, a public array whose length is part of its type. A breaking change bumps the 0.y before 1.0 (VERSIONING.md).
wai-quantum-qpu	0.3.0	0.4.0	Its functions take the engine's types (job::run, job::compiled_json), so it moves with the engine. Nothing else in it changes.
wai-quantum-cli	0.2.2	0.2.3	Its command line, MCP server and library only gain. It requires wai-quantum 0.8.0 and wai-quantum-qpu 0.4.0.
The job service	0.2.0	0.2.1	Its HTTP API and MCP server only gain.
wai-quantum (Python)	0.1.0	0.1.1	The 0.8.0 engine; its names are unchanged.
@transaction-science/wai-quantum	0.1.0	0.1.1	The 0.8.0 engine; its exports only gain.

The desktop app stays 0.1.0, and requires the new versions. Its installers are released with its update key.

What changes

• Manifests: each package's version; every requirement on them (the command line, the Python package, the desktop app, wai-quantum-qpu, and wai-rs's optional one); both server.json files; the JavaScript package's package.json and README; the requirement the engine's README shows and the wheel the Python README names, each with its translation.

• Seventeen lockfiles that resolve any of these crates, each read with --locked.

• The views page's manifest records the new digest of wai-quantum-views's lockfile. It was rebuilt with wai/wai-quantum-views/build.sh in the image CI rebuilds it in, and the page's bytes are unchanged.

• VERSIONING.md: the packages' versions today, and the example of what a result names.

• The changelog: a release heading over the six entries it carries (extension points, the GPU, scale-out, the variational library, QIR and jeff, pulse), with what a caller may have to change.

• Pins that move with the version. The engine's version is among the sealed bytes of a stamped result, as the comments beside each pin say:

  • the page's digests in wai-web/src/quantum_engine.rs: the course check 969b2c1c… → 1a9aa0ad…, the compile ac948133… → beffb3cb…, the estimate 8715e76b… → db90b147…;
  • the answer set's stored seal (bell-stored, bell-stored-changed and the bundle), written again with WAI_ANSWER_BUNDLE_WRITE=1, as at 0.7.0. wai breaking lists them as wire changes, and the changelog acknowledges each;
  • the five notebooks' stored outputs, stored again with check.sh --write-notebooks.

  The job pins strip the engine and schema, and do not move.

• The contract's baselines stay at the versions last published. A follow-up raises them once these are on crates.io.

Checked

Where	Result
macOS build host	Engine --features full --lib --tests: 1175 passed and every test binary. Contract set: 819 passed. Examples: 3 passed. wai-quantum-qpu: every target passed. CLI: 72 passed (bin) and every integration target; clippy -D warnings clean with and without default features; smoke, every check held; version --json names the engine 0.8.0. Service: 39 + 1 passed; smoke against a local instance, every check held; GET /v1 gives 0.2.1 with the engine 0.8.0. wai-web native quantum_engine: 29 passed; wasm32 under Node: 21 passed. The JavaScript package: built, packed as transaction-science-wai-quantum-0.1.1.tgz, its allow-list held, smoke passed, and the README's example ran installed by name.
Linux build host, in catthehacker/ubuntu:act-22.04	wai-quantum-py/ci/check.sh: 78 passed, 5 of 5 notebooks ran and matched (36 code cells), smoke passed.
Every lockfile	cargo metadata --locked reads each of the seventeen.
wai breaking --against 2860585f5	No unacknowledged breaking change.
Repository	The public-name check is clean.

Breaking

engine::schema::FILES (in the entries this release carries), and wai-quantum-qpu's functions that take the engine's types. Both are in the changelog with what a caller does.

🤖 Generated with Claude Code

The quantum packages' next release, as one change: versions, the changelog's release heading, every lockfile, and the pins that move with the engine's version. Once it merges, the crates are published, the command line is tagged (which builds its binaries, the Python wheels and the npm tarball), and the job service and the site are deployed from the merged commit. ## Versions | Package | Was | Now | Why | |---|---|---|---| | `wai-quantum` | 0.7.0 | 0.8.0 | Two entries this release carries change `engine::schema::FILES`, a public array whose length is part of its type. A breaking change bumps the 0.y before 1.0 (`VERSIONING.md`). | | `wai-quantum-qpu` | 0.3.0 | 0.4.0 | Its functions take the engine's types (`job::run`, `job::compiled_json`), so it moves with the engine. Nothing else in it changes. | | `wai-quantum-cli` | 0.2.2 | 0.2.3 | Its command line, MCP server and library only gain. It requires `wai-quantum` 0.8.0 and `wai-quantum-qpu` 0.4.0. | | The job service | 0.2.0 | 0.2.1 | Its HTTP API and MCP server only gain. | | `wai-quantum` (Python) | 0.1.0 | 0.1.1 | The 0.8.0 engine; its names are unchanged. | | `@transaction-science/wai-quantum` | 0.1.0 | 0.1.1 | The 0.8.0 engine; its exports only gain. | The desktop app stays 0.1.0, and requires the new versions. Its installers are released with its update key. ## What changes - **Manifests:** each package's version; every requirement on them (the command line, the Python package, the desktop app, `wai-quantum-qpu`, and `wai-rs`'s optional one); both `server.json` files; the JavaScript package's `package.json` and README; the requirement the engine's README shows and the wheel the Python README names, each with its translation. - **Seventeen lockfiles** that resolve any of these crates, each read with `--locked`. - **The views page's manifest** records the new digest of `wai-quantum-views`'s lockfile. It was rebuilt with `wai/wai-quantum-views/build.sh` in the image CI rebuilds it in, and the page's bytes are unchanged. - **`VERSIONING.md`:** the packages' versions today, and the example of what a result names. - **The changelog:** a release heading over the six entries it carries (extension points, the GPU, scale-out, the variational library, QIR and jeff, pulse), with what a caller may have to change. - **Pins that move with the version.** The engine's version is among the sealed bytes of a stamped result, as the comments beside each pin say: - the page's digests in `wai-web/src/quantum_engine.rs`: the course check `969b2c1c…` → `1a9aa0ad…`, the compile `ac948133…` → `beffb3cb…`, the estimate `8715e76b…` → `db90b147…`; - the answer set's stored seal (`bell-stored`, `bell-stored-changed` and the bundle), written again with `WAI_ANSWER_BUNDLE_WRITE=1`, as at 0.7.0. `wai breaking` lists them as wire changes, and the changelog acknowledges each; - the five notebooks' stored outputs, stored again with `check.sh --write-notebooks`. The job pins strip the engine and schema, and do not move. - **The contract's baselines stay** at the versions last published. A follow-up raises them once these are on crates.io. ## Checked | Where | Result | |---|---| | macOS build host | Engine `--features full --lib --tests`: 1175 passed and every test binary. Contract set: 819 passed. Examples: 3 passed. `wai-quantum-qpu`: every target passed. CLI: 72 passed (bin) and every integration target; clippy `-D warnings` clean with and without default features; smoke, every check held; `version --json` names the engine 0.8.0. Service: 39 + 1 passed; smoke against a local instance, every check held; `GET /v1` gives 0.2.1 with the engine 0.8.0. wai-web native `quantum_engine`: 29 passed; wasm32 under Node: 21 passed. The JavaScript package: built, packed as `transaction-science-wai-quantum-0.1.1.tgz`, its allow-list held, smoke passed, and the README's example ran installed by name. | | Linux build host, in `catthehacker/ubuntu:act-22.04` | `wai-quantum-py/ci/check.sh`: 78 passed, 5 of 5 notebooks ran and matched (36 code cells), smoke passed. | | Every lockfile | `cargo metadata --locked` reads each of the seventeen. | | `wai breaking --against 2860585f5` | No unacknowledged breaking change. | | Repository | The public-name check is clean. | ## Breaking `engine::schema::FILES` (in the entries this release carries), and `wai-quantum-qpu`'s functions that take the engine's types. Both are in the changelog with what a caller does. 🤖 Generated with [Claude Code](https://claude.com/claude-code)

dcharlot added 1 commit 2026-11-01 09:15:19 -05:00

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 ... 3c4b10a261

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]>

dcharlot added 1 commit 2026-11-01 12:00:48 -05:00

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

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]>

dcharlot added 1 commit 2026-11-01 18:38:22 -05:00

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

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]>

dcharlot added 1 commit 2026-11-01 20:40:55 -05:00

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

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]>

dcharlot merged commit b84ec74547 into main 2026-11-01 22:15:41 -05:00

dcharlot referenced this pull request from a commit 2026-11-01 22:15:42 -05:00

Merge pull request '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) from wai/quantum-release-0.8.0 into main

dcharlot referenced this pull request 2026-11-02 03:39:20 -05:00

wai-quantum-contract.yml: the baselines are the versions just published #569

Sign in to join this conversation.

Reviewers

No reviewers

Labels

Clear labels

No items

No labels

Milestone

Clear milestone

No items

No milestone

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

1 participant

Notifications

Subscribe

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference

Transaction-Science/open-standards!564

No description provided.