| Filename | Latest commit message | Latest commit date |
|---|---|---|
4d4c6dd147
All checks were successful
standards workspaces build + test / which workspaces this change touches (pull_request) Successful in 13s
wai-quantum command line / does this change touch it (pull_request) Successful in 16s
wai-quantum studio and desktop / does this change touch it (pull_request) Successful in 32s
wai-quantum command line / command line · linux (pull_request) Successful in 1m9s
repository checks / lockfiles, tests in CI, workflow hygiene, spec and section references, public text (pull_request) Successful in 2m4s
wai-quantum studio and desktop / studio · browser (pull_request) Successful in 2m41s
standards workspaces build + test / joule-code-rs (joule-code/joule-code-rs, joule-code-rs, linux-arm64, true) (pull_request) Successful in 10m11s
standards workspaces build + test / macOS energy backends (pull_request) Successful in 13m29s
wai-quantum command line / command line · macos (pull_request) Successful in 39s
wai-quantum studio and desktop / desktop app · macos (pull_request) Successful in 2m21s
The formulae job of the first full release run (wai-quantum-cli-v0.1.0) failed with a 403: it read each archive's .sha256 through its public download URL, and the public address refuses the Python library's default user agent. formulae.py now reads them at the forge's own address, the API's (over the private network, as the uploads go), with a user agent of its own. The formula and the manifest still point users at the public URLs. Run by hand against that release, it wrote both, which are attached there. Co-Authored-By: Claude Opus 5.5 <[email protected]> |
||
| .. | ||
| formulae.py | ||
| package.sh | ||
| publish.sh | ||