Pin qiskit < 1.0 #464
Merged
Pin qiskit < 1.0 #464
Conversation
This file contains 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
caleb-johnson
approved these changes
Dec 12, 2023
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.
The Qiskit 0.45 release notes say:
This PR proactively pins the version to
< 1.0, as suggested. Once nice thing about this is that is relieves a bit of pressure for us to fix issue #406 before Qiskit 1.0 is released on Jan 31. Also, if we are ready to support Qiskit 1.0 on that date, we can issue a patchlevel release easily that updates the pin to< 2.0.I've gone ahead and added a development version CI run against qiskit's
stable/0.46branch too, to essentially guarantee that there are no surprises when that is released.Updated README badges are visible at https://github.com/Qiskit-Extensions/circuit-knitting-toolbox/blob/pin-qiskit-0.X/README.md.