Run tests against Qiskit main to start preparing for Qiskit 2.0

[1ucian0]

Since the release of Qiskit 1.3 (Nov 2024), the Qiskit main branch has been preparing for the release of 2.0, a major release that will include breaking changes and is planned for March 2025. All the PRs merging into the main branch since Nov 2024 and until late Feb 2025 will be part of the 2.0 release. You can track the milestone progress here.

To prepare for this transition, it’s a good idea to start regularly running your tests against the main branch, similar to what qiskit-aer is doing here.

Running your tests weekly with Qiskit main and receiving notifications when something goes wrong allows you to proactively update your code (where alternative paths exist, they should already be available). Additionally, this provides valuable feedback for Qiskit developers—if you identify something that should not be a breaking change, you can notify the Qiskit team by, for example, submitting an issue.

For example, there are some usages of deprecated .DAGCircuit.duration and .DAGCircuit.unit triggered by the current tests that will break with the release of 2.0.

[jakelishman]

Qiskit main runs its tests against this package haha