Run tests agains Qiskit main to start getting ready for Qiskit 2.0

[1ucian0]

What is the expected enhancement?

Since the release of Qiskit 1.3 (Nov 2024), the Qiskit main branch has been preparing for the release of 2.0. Qiskit 2.0 is a major release that will include breaking changes and is planned for March 2025. 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 Aer is doing here.

Running your tests weekly with Qiskit main and getting notifications when something goes wrong allows you to proactively update your code (where alternative paths exist, they should already be available). Additionally, this serves as valuable feedback for Qiskit developers—if you encounter something that should not be a breaking change, you can let them know by, for example, submitting an issue.

[Tansito]

Thanks for this @1ucian0 , we will start taking a look into this 👍

cc: @pandasa123

[Tansito]

@1ucian0 we couldn't do the same as it was implemented in aer but we have a workaround: #1572

In this PR we are going to run all our tests over the main branch in Qiskit. At this moment everything is running and no breaking changes are affecting us. If we find out something we will let you know, thanks as always! 😄

[Tansito]

Closing this by now, if we find something we will let you know!