Updated changelog with QR rename #5419
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -10,17 +10,22 @@ in_page_toc_max_heading_level: 2 | |
|
|
||
| # Changelog | ||
|
|
||
| *Last updated 27 July 2026* | ||
|
|
||
| {/* remember to update the date in the previous line each time this page is updated!!! */} | ||
|
|
||
| Keep up with the latest and greatest from Qiskit and IBM Quantum®! | ||
|
|
||
| <Admonition type="note" title="What's new (last 60 days)"> | ||
|
|
||
| 27 July 2026 | ||
|
|
||
| - **Qiskit Runtime Service is now IBM Quantum Compute Service** — This is a naming change only and does not require any code changes or updates to existing applications. You may notice the new name throughout the user interface and documentation. [*Read more*](#qr-rename) | ||
| --- | ||
|
|
||
| 16 July 2026 | ||
|
|
||
| - **New pre-flight checks and new `backend` methods in Qiskit Functions v0.17.0** — Use the new methods in `qiskit-ibm-catalog` to check runtime capacity and backend access before you run, and `run()` now validates both before it submits a job. [*Read more*](new-methods) | ||
|
raulotaolea marked this conversation as resolved.
Outdated
|
||
| --- | ||
|
|
||
| 5 June 2026 | ||
|
|
@@ -34,14 +39,9 @@ Keep up with the latest and greatest from Qiskit and IBM Quantum®! | |
| 28 May 2026 | ||
|
|
||
| - **New Classroom Accounts** — Professors can now request a Classroom Account to manage and facilitate access for their students. With Classroom Accounts, students can use Open Plan resources without needing to provide personal credit card information. [*Read more*](#classroom-accounts) | ||
| </Admonition> | ||
|
|
||
| Jump to [IBM Quantum Platform](#latest-platform) | [Qiskit SDK](#latest-qiskit-sdk) | [Qiskit Runtime client](#latest-qiskit-runtime) | [IBM Quantum Compute Service](#latest-runtime-service) | [Qiskit Transpiler Service](#latest-qiskit-transpiler-service) | [Qiskit addons](#latest-qiskit-addons) | [Qiskit Functions](#latest-qiskit-functions) | [Qiskit Code Assistant](#latest-qca) | ||
|
|
||
|
|
||
|
|
||
|
|
@@ -50,6 +50,11 @@ Jump to [IBM Quantum Platform](#latest-platform) | [Qiskit SDK](#latest-qiskit-s | |
|
|
||
| This section summarizes the recent enhancements and new features for the new [IBM Quantum Platform](https://quantum.cloud.ibm.com/). | ||
|
|
||
| ### July 2026 | ||
|
|
||
| <span id="qr-rename"></span> | ||
| - **Qiskit Runtime Service is now IBM Quantum Compute Service** - Qiskit Runtime previously referred to both an internal runtime mechanism and IBM's managed execution service, creating confusion between open-source Qiskit and IBM's proprietary platform. The new naming clearly separates Qiskit, the open-source SDK for building portable quantum applications, from IBM Quantum Compute, the managed service for executing them on IBM quantum hardware. This provides a clearer architecture without changing workflows, APIs, access plans, or the customer experience. | ||
|
raulotaolea marked this conversation as resolved.
Outdated
|
||
|
|
||
| ### May 2026 | ||
|
|
||
| <span id="store-instruction"></span> | ||
|
|
@@ -448,9 +453,9 @@ Wondering what has changed? Read the [changelog](https://github.com/Qiskit/qiski | |
| *To see the release notes for all versions, visit the [Qiskit Runtime client release notes](/docs/api/qiskit-ibm-runtime/release-notes).* | ||
|
|
||
| <span id="latest-runtime-service"></span> | ||
| ## IBM Quantum Compute Service | ||
|
|
||
| This summary of the latest changes to the IBM Quantum Compute Service applies to anyone executing on IBM Quantum hardware, regardless of how you communicate with the service (by using `qiskit-ibm-runtime` or otherwise), or which version of the client SDK you use. | ||
|
Contributor
Author
There was a problem hiding this comment. @abbycross In this case, this section refers to the Qiskit Runtime execution environment that runs on the quantum computer itself. It does not refer to the service hosted on IBM Cloud. Therefore, Qiskit Runtime should be kept here. That said, we should avoid using the term "service" in this context to prevent confusion. Although it is technically a service—internally exposed through the Quantum System API (QSA), which both IQP and HPC integrations interact with at a low level—we want to clearly distinguish it from the IBM Cloud offering, now called IBM Quantum Compute Service. To make that distinction explicit, I suggest referring to it as IBM Qiskit Runtime. This makes it clear that we are talking about IBM's proprietary implementation of the Qiskit Runtime Execution Environment, rather than the IBM Cloud offering, now called IBM Quantum Compute Service.
Collaborator
There was a problem hiding this comment. We also have a section in the changelog called Qiskit Runtime client - are we distinguishing that with enough clarity in this case?
Collaborator
There was a problem hiding this comment. I think leaving it as Internally we often refer to the non-cloud part of the software stack as Qiskit Runtime, but I don't think that's true externally. Our product is listed as Qiskit Runtime Service, and the first thing you initialize in the client SDK is My proposal is to take this opportunity and combine the existing Qiskit Runtime and IQP sections under a single header -
Collaborator
There was a problem hiding this comment. My suggestion was actually to merge the existing
Collaborator
There was a problem hiding this comment. I've taken a stab at combining the two as Jessie suggests, and interleaved the archival entries.
Collaborator
There was a problem hiding this comment. Since this PR doesn't have a preview, here are screenshots from my local build
Contributor
Author
There was a problem hiding this comment. I wrote the text in the screenshot assuming we would keep a dedicated section for Qiskit Runtime, understood as the execution environment, and I prefixed it with IBM to make it clear that it refers to IBM's implementation of Qiskit Runtime. Now that we've decided to simplify the model and present IBM Quantum Compute Service as the main concept, I'm not sure whether that explanation still makes sense. My original intention was simply to explain the different components involved in the execution flow and how they relate to each other. Do you think it's still worth describing those underlying components in this context, even if we don't expose them elsewhere or have dedicated sections for them? Or would you rather treat IBM Quantum Compute Service as a black box and avoid introducing those implementation details altogether? If we go with the latter approach, we could write something along these lines:
Contributor
Author
There was a problem hiding this comment.
I agree with merging the existing Qiskit Runtime section into IBM Quantum Compute Service. That aligns well with the goal of simplifying the terminology presented to users. However, I don't think the same applies to the IBM Quantum Platform section. Regardless of the rename itself, from a product perspective I think it's important that we continue to distinguish between the platform and the services it provides. IBM Quantum Platform is the platform. IBM Quantum Compute Service is one of the services within that platform. They represent different layers of the product hierarchy, and I think our changelog should reflect that distinction rather than hide it. Otherwise, platform-level changes -- such as documentation, learning content, Composer, and similar capabilities -- would gradually end up being described as changes to IBM Quantum Compute Service, even though they belong to IBM Quantum Platform. |
||
|
|
||
| ### January 2026 | ||
| - [**Directed execution model.**](/docs/guides/directed-execution-model) This new execution model allows you to fine-tune error mitigation and other techniques without sacrificing performance by providing the ingredients to capture design intents on the client side, and shifting the costly generation of circuit variants to the server side. For example, you can use the [Samplomatic library](https://qiskit.github.io/samplomatic/index.html) to define the exact layers in your circuits to apply Pauli-twirling and to inject noise. The new [Executor primitive](/docs/guides/directed-execution-model#executor-primitive) will then follow your directives to generate and execute the randomized circuit variants in Qiskit Runtime. | ||
|
|
@@ -737,4 +742,4 @@ To get started, explore the [Qiskit Functions documentation](/docs/guides/functi | |
| For more details on Qiskit Code Assistant, see the [documentation](/docs/guides/qiskit-code-assistant). | ||
|
|
||
| </AccordionItem> | ||
| </Accordion> | ||
Uh oh!
There was an error while loading. Please reload this page.