Consider removing the patch version from the version selector

URL to the relevant guide or resource

https://quantum.cloud.ibm.com/docs/en/api/* like https://quantum.cloud.ibm.com/docs/en/api/qiskit-ibm-runtime and https://quantum.cloud.ibm.com/docs/en/api/qiskit/

Select all that apply

• new content request
• typo
• code bug
• out-of-date content
• broken link
• other

Describe the fix or the content request.

The version selector shows (correctly) the last patch version of each minor release without showing the old patch versions (for example, v2.3.1 is there, but v2.3.0 is not there). This selector points to a URL without the patch version (for example, v2.3.1 points to quantum.cloud.ibm.com/docs/en/api/qiskit/2.3/...). Since the numbers between the dots in the versions are currently similar, I often have to think twice before selecting the right option.

I think it would be great if the patch version were not shown in the selector (i.e., v2.3 instead of v2.3.1). The patch version provides no extra information and clutters the selector a bit.

For new content requests - if the request is accepted, do you want to write the content?

(No answer)

Start by opening the API documentation URLs in the issue and tracing where the version selector is configured or rendered. Update the selector so each minor release is labeled without its patch number, while confirming its links still resolve to the corresponding versioned documentation URLs.