Skip to content
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

Bump qpy version in dump() calls after Qiskit is updated server side #1410

Closed
mtreinish opened this issue Feb 15, 2024 · 0 comments · Fixed by #1522
Closed

Bump qpy version in dump() calls after Qiskit is updated server side #1410

mtreinish opened this issue Feb 15, 2024 · 0 comments · Fixed by #1522
Assignees
Labels
enhancement New feature or request
Milestone

Comments

@mtreinish
Copy link
Member

What is the expected feature or enhancement?

Until we have a proper solution for #1375 so that the we can do version negotiation in the client directly we will need to manually bump the qpy version to leverage new features and bugfixes from new format revisions. This will involve changing 10 here:

https://github.com/Qiskit/qiskit-ibm-runtime/blob/main/qiskit_ibm_runtime/utils/json.py#L222

and

https://github.com/Qiskit/qiskit-ibm-runtime/blob/main/qiskit_ibm_runtime/utils/json.py#L252

to 11. We can only do this once the server side has updated to Qiskit 1.0.0 though as it is a requirement to have qiskit >=1.0.0 to parse qpy version 11.

Acceptance criteria

Qiskit 1.0.0 is deployed in production everywhere

@mtreinish mtreinish added the enhancement New feature or request label Feb 15, 2024
@kt474 kt474 self-assigned this Mar 15, 2024
@kt474 kt474 added this to the 0.22.0 milestone Mar 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants