Update qiskit-ibm-runtime requirement from ~=0.20.0 to ~=0.23.0

[dependabot]

Updates the requirements on qiskit-ibm-runtime to permit the latest version.

Release notes

Sourced from qiskit-ibm-runtime's releases.

Qiskit IBM Runtime 0.23.0

Changelog

Deprecated

• Deprecate backend.run (#1579)
• Update from_id() (#1311)

Added

• Add twirling options to SamplerV2 (#1583)
• Raise an error if dynamical decoupling is used with dynamic circuits (#1593)
• Level 1 measurement support in Sampler options (#1594)
• Add elapsed_time to session details (#1581)
• Pretty print options (#1538)
• feat: Add qctrl validation for Primitives v2 (#1550)

Fixed

• Missing circuit metadata in PubResult from SamplerV2 (#1596)
• Decode empty Databin's (#1580)
• Custom header not being sent (#1592)
• ZNE options validation fix (#1588)
• Use status() for related methods (#1568)
• Allow new job status' in RuntimeJobV2 (#1494)
• Fix incorrect specification of noise_gain option (#1575)
• Fix issue with encoding ParameterExpression (#1536)

Commits

• f9b860e Prepare release 0.23.0 (#1620)
• d456084 Deprecate backend.run (#1579)
• a2a803e keep old behavior for backend.run (#1618)
• 7c9979e Add twirling options to SamplerV2 (#1583)
• be51a45 Missing circuit metadata in PubResult from SamplerV2 (#1596)
• 4af7729 Raise an error if dynamical decoupling is used with dynamic circuits (#1593)
• 0d77bbe Remove tutorials (#1599)
• e460157 minor doc fix in IBMBackend (#1614)
• ce84bf6 Fix a random seed of tests for BackendEstimatorV2 (#1616)
• 8f9a59e Deprecate V1 primitives (#1591)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[cosenal]

@andre-a-alves Do you think we can bump this to at least 0.21.2? It would be important to fix the security issue opened here

[andre-a-alves]

Anything starting with 0.21+ appeared to have conflicts with pennylane-qiskit. I'd have to take some time to dig deeper to see if it's possible at this time.

[cosenal]

@andre-a-alves I assigned this to you and I added a comment to the pennylane-qiskit related issue.

[andre-a-alves]

Sorry - I meant to push to a branch on my fork; not this one. I reverted my change

[andre-a-alves]

Leaving what I've found for the record - this is not yet resolved.

• qiskit-ibm-runtime 0.23.0 installs pydantic 2.7.1, which is not compatible with amazon-braket-sdk 1.69.0, but is compatible with amazon-braket-sdk 1.78.0.
• pydantic 2.7.1 is also not compatible with qcs-api-client 0.21.6, but I am not sure, yet, which dependency installs that.
• pennylane-qiskit continues to say it is incompatible with qiskit-ibm-runtime >0.20.x.
• If the two changes above are manually installed with pip install --force-reinstall "qiskit-ibm-runtime==0.23.0" "amazon-braket-sdk==1.78.0", all our unit tests pass. dev_requirements.txt will not install with the conflicts, but there are at least manual, work-around steps to avoid the security vulnerability.

[cosenal]

Thanks, @andre-a-alves.

pydantic 2.7.1 is also not compatible with qcs-api-client 0.21.6, but I am not sure, yet, which dependency installs that.

Here is its pipdeptree report:

qcs-api-client==0.21.6
└── pyquil==3.5.4 [requires: qcs-api-client>=0.21.0,<0.22.0]
    └── cirq-rigetti==1.3.0 [requires: pyquil>=3.2.0,<4.0.0]
        └── cirq==1.3.0 [requires: cirq-rigetti==1.3.0]
            └── mitiq==0.36.0.dev0 [requires: cirq>=1.0.0,<1.4.0]

The reason why we can't upgrade to amazon-braket-sdk 1.78.0 yet is also about qcs-api-client and pydantic, see #2310

A recap on the chain of dependency events we are wishing for :)

• Cirq upgrades to PyQuil v4 (PR open)
• PyQuil v4 supports qcs-api-client==0.25.1, which in turns depends on pydantic = "^2.6.3", which means pydantic 2.7.1 can be installed.
• and at the point, qiskit-ibm-runtime can be bumped to >0.20.x 🤞

Note that in #2303 I started splitting our dependencies, so that in the future we don't end up in this kind of dependency hell. However, even if that PR gets merged, the development environment still has all the dependencies mixed up.