We have several links in our guides to things that will be removed in Qiskit 2.0, such as many of the links in #2705.
We should proactively update these links to be /api/qiskit/1.4, which will currently redirect to /api/qiskit. Once 2.0 is released, /api/qiskit/1.4 will become the new stable link.
This issue is meant to minimize the changes necessary for March 20 to make the launch less stressful.
We need to teach the link checker that the /api/qiskit/1.4 links are valid. Given how temporary it is, we probably want to use the allowlist mechanism in ignores.ts for that.
--
Relates to #2714. To test this out, try switching the docs for Qiskit SDK latest to the 2.0.0rc1 release (by using npm run gen-api) then run the link checker.
--
We should check if other APIs break, like Runtime.
We have several links in our guides to things that will be removed in Qiskit 2.0, such as many of the links in #2705.
We should proactively update these links to be
/api/qiskit/1.4, which will currently redirect to/api/qiskit. Once 2.0 is released,/api/qiskit/1.4will become the new stable link.This issue is meant to minimize the changes necessary for March 20 to make the launch less stressful.
We need to teach the link checker that the
/api/qiskit/1.4links are valid. Given how temporary it is, we probably want to use the allowlist mechanism inignores.tsfor that.--
Relates to #2714. To test this out, try switching the docs for Qiskit SDK latest to the 2.0.0rc1 release (by using
npm run gen-api) then run the link checker.--
We should check if other APIs break, like Runtime.