Skip to content

Pin Qiskit to <2 in next release (backport #904) #935

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
May 22, 2025

Conversation

mergify[bot]
Copy link
Contributor

@mergify mergify bot commented May 22, 2025

Summary

Pinning Qiskit<2 will avoid breaking changes to affect current installations. This potential effect was raised in #897. The constraint can be removed when QML achieves full compatibility with Qiskit 2.


This is an automatic backport of pull request #904 done by [Mergify](https://mergify.com).

* Pin Qiskit to `<2` in next release

* Update constraints.txt

* Update requirements.txt

(cherry picked from commit de2cf2c)

# Conflicts:
#	requirements.txt
@mergify mergify bot added the conflicts label May 22, 2025
Copy link
Contributor Author

mergify bot commented May 22, 2025

Cherry-pick of de2cf2c has failed:

On branch mergify/bp/stable/0.8/pr-904
Your branch is up to date with 'origin/stable/0.8'.

You are currently cherry-picking commit de2cf2c.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Changes to be committed:
	modified:   constraints.txt

Unmerged paths:
  (use "git add <file>..." to mark resolution)
	both modified:   requirements.txt

To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally

@woodsp-ibm woodsp-ibm merged commit ba0545c into stable/0.8 May 22, 2025
9 of 14 checks passed
@edoaltamura edoaltamura deleted the mergify/bp/stable/0.8/pr-904 branch May 22, 2025 20:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants