Release Notes¶

+
+

Upcoming release (stable/0.7)¶

+
+

Prelude¶

+

The 0.7.3 release fixes the circuit cutting code to be compatible +with the forthcoming Qiskit 1.2 release. It also pins numpy to +version 1.X, as DOCplex (which is used by the legacy CutQC +implementation) is incompatible with numpy 2.0.

+
+
+

Bug Fixes¶

+
    +
  • The circuit cutting module now uses a stringified UUID instead of +a UUID object when it needs to generate a unique label for +circuit barriers during processing, as the forthcoming Qiskit 1.2 +release requires that labels always be a string.

  • +
+
+

0.7.2¶

-
-

Prelude¶

+
+

Prelude¶

The 0.7.2 release includes two improvements to the automated cut finder: a performance enhancement, and a fix to a bug that occurs when the cut finder finds a solution where both incoming wires to a @@ -326,15 +345,15 @@

-

0.7.1¶

+

0.7.1¶

-

Prelude¶

+

Prelude¶

The 0.7.1 release provides a workaround to ensure that the experiments generated by the circuit cutting workflow will execute on IBM Quantum’s hardware backends.

-
-

Bug Fixes¶

+
+

Bug Fixes¶

  • Added a workaround so that the classical registers in the generated circuits will always contain at least one bit. This is @@ -343,16 +362,16 @@

-

Other Notes¶

+

Other Notes¶

-

0.7.0¶

+

0.7.0¶

-

Prelude¶

+

Prelude¶

The 0.7 release introduces an automated cut finding code for the new circuit cutting workflow. With this milestone, the older cutting workflow (CutQC) is now deprecated. Additionally, this is the first CKT release to support version 2 of the Qiskit Runtime primitives. User are encouraged to migrate to v2 primitives as soon as possible.

@@ -406,7 +425,7 @@