Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[R02] Cap the Qiskit major version in the qiskit requirement

Open Beginner friendly
#116 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
92/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Domain
build-system

Research direction

Open requirements-qiskit.txt and inspect the qiskit requirement. Add the major-version cap shown in the issue, then verify the requirement is valid; the ecosystem checkup should clear after the change is merged and the next weekly run completes.

Written by the indexing model from the issue text.

Description

Hi! benchpress 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 file

The qiskit requirement in requirements-qiskit.txt allows a not-yet-released major version of Qiskit

qiskit>=1.3.0rc1 has no upper bound, so pip is free to install the next major release the day it lands:

-qiskit>=1.3.0rc1
+qiskit>=1.3.0rc1,<3

If benchmarking whatever Qiskit is newest is the point of this file, that is a fine answer: say so and I will record it as an explanation on the ecosystem side instead.

Otherwise 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
OpenQASM
Stars
164
Forks
42
PR merge metrics
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Qiskit/benchpress

All issues in Qiskit/benchpress

Similar issues

More Build System issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.