Temporarily pin qiskit-nature < 0.7#435
Merged
Merged
Conversation
caleb-johnson
approved these changes
Oct 10, 2023
Collaborator
caleb-johnson
left a comment
caleb-johnson
left a comment
There was a problem hiding this comment.
Thanks for taking care of this!
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
2 participants
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.
Until #408 is merged (and #406 is thus fixed), we know that CKT will not work with Qiskit Nature 0.7 (a release that is expected some time soon). We might as well preemptively mark our CKT releases until #408 is merged as being incompatible with Qiskit Nature 0.7. Otherwise, users might be unpleasantly surprised once Qiskit Nature 0.7 is released and entanglement forging no longer works.
As an alternative, we could just prioritize getting #408 in shape to merge, but there's no harm in having this pinned until that happens.
TODO