Conversation
CUDA-Q 0.16.0 is released; make it the minimum. The wheel's declared range, the CI pip install range, and the Custom-mode wheel version placeholder move together. Full-suite validation against the released cudaq==0.16.0 wheel was run ahead of this change (472 passed / 3 skipped on the primitives line, which includes every test on main); v0.1.0-era functionality needs no code changes on 0.16. The one 0.16-sensitive construction (1-bit- address QROM lookups) ships with its own protection — the dispatch- pruning commit already on the QROM PR (NVIDIA#40) — so this change and NVIDIA#40 can merge in either order; open PRs adopt the new range only when they rebase, at which point they inherit that commit too. The .cudaq_version pin bump to the 0.16.0 release commit is split into a follow-up: its first firing of the from-source lanes surfaced a build-layout change in the 0.16 source tree (the built install no longer exposes the python package on the expected prefix path), which the build plumbing must adapt to before the pin can move. Signed-off-by: Scott Thornton <wsttiger@gmail.com>
wsttiger
force-pushed
the
fix/bump_cudaq_0_16
branch
from
September 14, 2026 20:32
afffda8 to
b76976b
Compare
anjbur
requested changes
Sep 15, 2026
anjbur
left a comment
Collaborator
There was a problem hiding this comment.
We'll also need to bump the 0.15.99 version used in get-cudaq-wheels/action.yaml up to 0.16.99. Otherwise, the CI will break for Custom wheel builds.
The version bump to cudaq 0.16 missed the release_version build-args in get-cudaq-wheels/action.yaml; Custom wheel builds would break otherwise (review from anjbur on PR NVIDIA#50). Signed-off-by: Scott Thornton <wsttiger@gmail.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
CUDA-Q 0.16.0 is released; this makes it the minimum supported
version. Four coordinated changes:
pyproject.toml: the wheel now declarescudaq >= 0.16.0, < 0.17.PRs test exactly the claim the wheel ships).
stay above the released version line.
Validation
cudaq==0.16.0wheel ahead ofthis PR: 472 passed / 3 skipped on the primitives line (a superset
of every test on main). v0.1.0-era functionality requires no code
changes on 0.16.
the unary-iteration feature) ships with its own protection — the
dispatch-pruning commit already on Add unary-iteration and QROM primitives #40 — so this PR and Add unary-iteration and QROM primitives #40 can
merge in either order. Open PRs adopt the new range only when they
rebase, at which point they inherit that commit too.
and run the full suite against it.
.cudaq_versionpin bump is deliberately split into a follow-upPR: its first firing of the from-source lanes surfaced a
build-layout change in the 0.16 source tree (built install no longer
exposes the python package on the expected prefix path) — the lanes
doing exactly the job Test PRs against released cudaq; from-source becomes a manual probe #42's review designed them for. The pin moves
once the build plumbing adapts.
Notes
release tag); with the pruning commit merged, nothing in this
library triggers it.
kernels; follow-up modernization (composed select_swap, composition
contract) is staged on
features/primitives_016_refactorand landsseparately after this.