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

dcharlot commented 2026-11-04 15:47:49 -05:00

Owner

Copy link

The release of the WAI Quantum packages that carries the provider jobs (#590), the idempotency key (#607), the resumable optimisation (#608), the provider jobs as MCP tasks on the command line (#609), the job service's rerun (#613) and its MCP tasks (#615).

Versions

Each change only adds or fixes, so each package moves its last number (wai/wai-quantum/VERSIONING.md, "Before 1.0"):

Package	From	To
wai-quantum	0.8.0	0.8.1
wai-quantum-qpu	0.4.0	0.4.1, requiring wai-quantum 0.8.1
wai-quantum-cli	0.2.3	0.2.4, requiring both
The job service	0.2.1	0.2.2
The Python package	0.1.1	0.1.2

@transaction-science/wai-quantum stays 0.1.1, since nothing in it changed, and the desktop app stays 0.1.2.

What moves with them

• Every dependent's requirement, both server.json files, and the seventeen lockfiles that resolve any of the packages, each read with --locked.
• The changelog's release heading, above the six entries it carries.
• The engine's version is among a stamped result's sealed bytes, so the views page's pinned digests move: the course check, the compile and the estimate, each regenerated from the test's own output. 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.
• Beyond the 0.8.0 release's list: the Python README's wheel name, and the views manifest and page (build.sh). The 0.8.0 release needed both as follow-up commits.

Checked

On the build host:

• cargo-semver-checks 0.51.0 for wai-quantum, wai-quantum-qpu and wai-quantum-cli against their published versions, as CI's API job runs it: no semver update required.
• Every touched lockfile reads with --locked.
• The engine's tests with every feature (the receipt pins, the schema tests and the answer conformance); wai-web's quantum_engine tests, native and wasm32; the views crate and build-views.mjs --check.
• The command line's tests, the job service's tests and the qpu tests.
• check_schemas.py against the release binary, which reports engine 0.8.1.
• The Python package's ci/check.sh, the notebooks run and matched among them.
• The quantum docs' checker, over every document.

The public-name check is clean, and so are this description and the commit message.

After it merges: publish wai-quantum, then wai-quantum-qpu, then wai-quantum-cli, then the Python package, from a clean main.

🤖 Generated with Claude Code

The release of the WAI Quantum packages that carries the provider jobs (#590), the idempotency key (#607), the resumable optimisation (#608), the provider jobs as MCP tasks on the command line (#609), the job service's rerun (#613) and its MCP tasks (#615). ## Versions Each change only adds or fixes, so each package moves its last number (`wai/wai-quantum/VERSIONING.md`, "Before 1.0"): | Package | From | To | |---|---|---| | `wai-quantum` | 0.8.0 | 0.8.1 | | `wai-quantum-qpu` | 0.4.0 | 0.4.1, requiring `wai-quantum` 0.8.1 | | `wai-quantum-cli` | 0.2.3 | 0.2.4, requiring both | | The job service | 0.2.1 | 0.2.2 | | The Python package | 0.1.1 | 0.1.2 | `@transaction-science/wai-quantum` stays 0.1.1, since nothing in it changed, and the desktop app stays 0.1.2. ## What moves with them - Every dependent's requirement, both `server.json` files, and the seventeen lockfiles that resolve any of the packages, each read with `--locked`. - The changelog's release heading, above the six entries it carries. - The engine's version is among a stamped result's sealed bytes, so the views page's pinned digests move: the course check, the compile and the estimate, each regenerated from the test's own output. 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. - Beyond the 0.8.0 release's list: the Python README's wheel name, and the views manifest and page (`build.sh`). The 0.8.0 release needed both as follow-up commits. ## Checked On the build host: - `cargo-semver-checks` 0.51.0 for `wai-quantum`, `wai-quantum-qpu` and `wai-quantum-cli` against their published versions, as CI's API job runs it: no semver update required. - Every touched lockfile reads with `--locked`. - The engine's tests with every feature (the receipt pins, the schema tests and the answer conformance); wai-web's `quantum_engine` tests, native and wasm32; the views crate and `build-views.mjs --check`. - The command line's tests, the job service's tests and the qpu tests. - `check_schemas.py` against the release binary, which reports engine 0.8.1. - The Python package's `ci/check.sh`, the notebooks run and matched among them. - The quantum docs' checker, over every document. The public-name check is clean, and so are this description and the commit message. After it merges: publish `wai-quantum`, then `wai-quantum-qpu`, then `wai-quantum-cli`, then the Python package, from a clean main. 🤖 Generated with [Claude Code](https://claude.com/claude-code)

dcharlot added 1 commit 2026-11-04 15:47:49 -05:00

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 ... a274776b50

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

dcharlot referenced this pull request from a commit 2026-11-04 17:41:28 -05:00

joule-moq-web: a turn a later schedule replaces ends at that schedule's from, and a performer's page keeps its guard before it

dcharlot referenced this pull request 2026-11-04 17:43:37 -05:00

joule-moq-web: a turn a later schedule replaces ends at that schedule's from #620

dcharlot merged commit 98192fe63e into main 2026-11-04 19:25:16 -05:00

dcharlot referenced this pull request from a commit 2026-11-04 19:25:18 -05:00

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

dcharlot referenced this pull request 2026-11-04 19:28:00 -05:00

wai-quantum-contract.yml: the baselines are 0.8.1, 0.2.4 and 0.4.1, the versions just published #621

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!619

No description provided.