[R02] Cap the Qiskit major version in the qiskit requirement
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 95/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- cpp
- Domain
- build-system
Research direction
Update the qiskit requirements in requirements.txt and requirements-dev.txt as described in the issue, matching the existing numpy cap format. Verify both files contain the capped requirement; the Qiskit Ecosystem checkup should clear after the merged change is picked up by its next weekly run.
Written by the indexing model from the issue text.
Description
Hi! qiskit-cpp is a Qiskit Ecosystem member, and a new weekly check up, first run this Thursday, does not pass for it:
[R02]Have a cap on the major version for the qiskit dependency in the requirements fileThe qiskit requirement in requirements.txt allows a not-yet-released major version of Qiskit
Both files that name qiskit are uncapped, so pip is free to install the next major release the day it lands. In requirements.txt, next to the cap you already have on numpy:
-qiskit>=2.1.0
+qiskit>=2.1.0,<3
and in requirements-dev.txt, where the requirement is a bare qiskit:
-qiskit
+qiskit>=2.1.0,<3
Bump the cap once you have tested against the next major release. The check up reads the requirements files on your default branch, so it clears on its own at the next weekly run after the change is merged.
Thanks for being part of the ecosystem!
- Dominant language
- C++
- Stars
- 41
- Forks
- 27
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Qiskit/qiskit-cpp
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Qiskit/qiskit-cpp#140 · 2 comments ·
-
Difficulty 5/5 Over a week Newbie friendliness 45/100
Qiskit/qiskit-cpp#166 ·
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 52/100
Qiskit/qiskit-cpp#165 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 64/100
Qiskit/qiskit-cpp#163 · 1 comment ·
-
Difficulty 3/5 1-2 days Newbie friendliness 58/100
Qiskit/qiskit-cpp#162 ·
All issues in Qiskit/qiskit-cpp
Similar issues
-
Incorrect Link in README.mdPossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 1/5 Under an hour Newbie friendliness 95/100
flameshot-org/flameshot#4996 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
utopia-rise/godot-jvm#1004 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 3 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 1 day
-
chore(build): TxCoordinator.cpp uses the deprecated shared_ptr atomic free functionsPossibly taken @w5jwp claimed this today. Open
Difficulty 1/5 Under an hour Newbie friendliness 84/100
aethersdr/AetherSDR#6368 · 1 comment ·
Maintainers usually reply within 1 day