Skip to content

Commit

Permalink
Include upgrading to Qiskit 1.0 on install page (Qiskit#634)
Browse files Browse the repository at this point in the history
Closes Qiskit#631 

To be merged once Qiskit 1.0 is live and not earlier.

---------

Co-authored-by: Eric Arellano <[email protected]>
  • Loading branch information
abbycross and Eric-Arellano authored Feb 15, 2024
1 parent 435ae6c commit ba213c8
Show file tree
Hide file tree
Showing 2 changed files with 11 additions and 0 deletions.
1 change: 1 addition & 0 deletions cSpell.json
Original file line number Diff line number Diff line change
Expand Up @@ -155,6 +155,7 @@
"Unroller",
"Vazirani",
"Vedral",
"venv",
"Watrous",
"Weyl",
"Woerner",
Expand Down
10 changes: 10 additions & 0 deletions docs/start/install.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -8,6 +8,16 @@ description: Install and set up Qiskit and Qiskit Runtime on various operating s

Whether you will work locally or in a cloud environment, the first step for all users is to install Qiskit&reg;. For those wanting to run on a real system, your next step is to choose one of two channels in order to access IBM Quantum&trade; systems: IBM Quantum Platform or IBM Cloud&reg;.

<Admonition type="caution" title="Upgrade from Qiskit 0.x to Qiskit 1.0 and beyond">
(If you are installing Qiskit for the first time, skip ahead to the [Install and set up](#local) section. This notice is relevant only to users who have installed Qiskit previously.)

**For those upgrading from version 0.x to 1.0 or later**: note that because Qiskit 1.0 uses a new packaging structure, you **cannot** use `pip install -U qiskit` to upgrade from any Qiskit 0.x version to 1.0.

See the [Qiskit 1.0 migration guide](/api/migration-guides/qiskit-1.0) for details and instructions.

Future updates starting with Qiskit 1.0 will allow for in-place upgrades.
</Admonition>

<span id="local"></span>
## Install and set up Qiskit with the Qiskit Runtime client

Expand Down

0 comments on commit ba213c8

Please sign in to comment.