Unitary ucc 0.4.11 Pins Python and Qiskit for Compiler CI

What changed

The Unitary Foundation shipped ucc v0.4.11 on 31 October 2026. UCC is an open quantum compiler that routes circuits across backends. This patch release pins Python below 3.14 and bumps core dependencies. Those bumps include Qiskit 2.2.2 and pytket 2.10.2.

The release notes live on the ucc GitHub releases page. The tag points to commit 872badc.

Release 0.4.11 is a maintenance train item, not a new algorithm headline. Still, maintenance releases gate production jobs. A silent Qiskit bump can change transpile depth on the same circuit diagram. Teams that pin only major versions learn that lesson during overnight batch failures.

Why it matters

Compiler stacks break when Python or Qiskit moves without warning. Teams running hybrid jobs across IBM Quantum and other SDKs feel that pain first. A pinned compiler release gives a fixed point for CI images before year end refactors.

Quantum program leads use UCC to compare transpile paths. Dependency pins reduce surprise failures when interns upgrade laptops. They do not replace backend calibration checks on real devices.

Hybrid HPC groups also use UCC to route jobs across simulators and cloud QPUs. When Python 3.14 lands on developer machines, unpinned tools break first. Pinning below 3.14 gives teams time to test wheels and CUDA pairs before they flip the cluster default.

Who is affected

Platform engineers who maintain shared conda or uv environments for research groups should read the pin list. Vendors who ship tutorial notebooks on UCC should bump their lockfiles. Educators running fall labs need images that match the new Python ceiling.

What to do next

Schedule a dry run transpile job on your standard benchmark circuits with v0.4.11. Log pass depth and wall time against v0.4.10. If you freeze images monthly, add this tag to the November build.

If you mix pytket and Qiskit in one pipeline, rerun integration tests noted in the release changelog. Report regressions upstream rather than patching locally without a ticket.

Archive the prior container tag in your registry. Document the upgrade in your internal change log so auditors can tie job outputs to compiler versions. Small tooling moves often explain sudden drift in benchmark tables during grant reporting season.

What to watch

Watch the next minor release for benchmark workflow changes tied to the ucc-bench repo. Watch IBM Runtime releases that may require matching Qiskit pins. Watch whether Python 3.14 support lands with explicit test matrices.

Watch your cloud vendor images for silent ucc upgrades. Pin the compiler tag in workflow YAML the same way you pin driver versions.

Note the release date in your internal wiki. Future you will need it when a job result shifts and audit asks why.

Photo: Michael Dziedzic / Pexels

Photo: National Cancer Institute / Pexels

Teams that skip patch notes often debug transpile diffs by hand. That work is slow and easy to misread. A short upgrade ticket with before and after depth logs saves a day when a grant deadline is near.

If you teach quantum labs, align student images with 0.4.11 before spring term starts. Students on mixed laptops will otherwise mix Python 3.14 previews with older wheels and get opaque import errors on Monday mornings.

Copy the dependency table from the release page into your lab handbook. Future TAs will not dig through GitHub tags during their first week.

Sources

• Primary — GitHub, ucc v0.4.11 release notes (31 October 2026). Lists dependency pins and version tag.
• Secondary — GitHub, ucc release index (31 October 2026). Confirms release date ordering against prior tags.