Skip to content

docs: robot stack 9.1.0#21677

Open
ecormany wants to merge 3 commits into
edgefrom
docs-release-9.1.0
Open

docs: robot stack 9.1.0#21677
ecormany wants to merge 3 commits into
edgefrom
docs-release-9.1.0

Conversation

@ecormany
Copy link
Copy Markdown
Contributor

@ecormany ecormany commented Jun 5, 2026

Overview

PR collecting all documentation that is timed with the RS 9.1.0 release (and the OT-2 26.6 release, and the very quickly following PD releases).

Test Plan and Hands on Testing

Sandbox

Changelog

  • See commit log of squashed and merged PRs.
  • Touch-up commits as needed to get strict docs build working.

Review requests

  • We'll review for completeness and accuracy before making a staging tag.

Risk assessment

low-med, lots of docs together.

jwwojak and others added 3 commits June 2, 2026 09:06
# Overview

This explains how to downgrade OT-2 robot software. It attempts to
explain how to

- Downgrade from 26.06 to an earlier version
- Downgrade from v9.0 to and earlier version

We're not recommening running multiple versions of the App on the same
machine. This gets complex, particularly with Windows. Easier on Linux
and Mac, but maybe not a good practice.

**Sandbox:**
https://sandbox.docs.opentrons.com/downgrade-ot2-software-instructions/ot-2/opentrons-app/ot2-downgrade/

RTC-990

## Test Plan and Hands on Testing

- Check links.

## Changelog

Adds a new doc, `ot2-downgrade.md` to the Opentrons App section of the
OT-2 manual.

## Review requests

- Does the procedure seem clear and accurate.

## Risk assessment

- Low, because docs only.
- Medium, because this can get complicated.

---------

Co-authored-by: emilyburghardt <emily.burghardt@opentrons.com>
# Overview

This PR adds: 

- a description of step groups (and a screenshot) to protocol viz in the
Flex manual _(note that this docs build will continue to fail due to
links to `groups.md` in the API docs, which exists only in
`chore_release-9.1.0`)_
- updated links to the liquid classes section of the API docs, to be
added in #21489 _(again, this docs build will fail because this branch
doesn't know those links have been updated)_
- updates to PAPI-exclusive features in the Flex manual: mainly, that
partial tip pickup is no longer exclusive to PAPI. I removed this from
PAPI-exclusive features and instead added a brief description to
`protocols/designer.md`


This PR targets `docs-release-9.1.0`, so it could be merged in while
failing if we feel that the syntax here is correct!

## Test Plan and Hands on Testing


[sandbox](https://sandbox.docs.opentrons.com/docs-flex-step-groups-and-more/)

## Changelog

See above.

## Review requests

Is the syntax correct (so this can be merged into our isolated docs
release branch even if the build fails)?

## Risk assessment

should get a close look at the liquid classes links. I updated the
structure simply to clean up the left hand side in the API docs in PR
#21489 ; summary below as well:

the new folder `python-api/docs/liquid-classes`, which contains: 
-  a folder `lc_icons` for the images for the properties table
- new file `customize.md` (same text as [Customizing Liquid
Classes](https://docs.opentrons.com/python-api/liquid-classes/#customizing-liquid-classes))
- new file `definitions.md` (same text/tables as [Liquid Class
Definitions](https://docs.opentrons.com/python-api/liquid-class-definitions/)
- new file `index.md`
- new file `liquid-classes.md` (like in the current liquid classes
[page](https://docs.opentrons.com/python-api/liquid-classes/#opentrons-verified-liquid-classes))
- new file `using-liquid-classes.md` (same text as [Using Liquid
Classes](https://docs.opentrons.com/python-api/liquid-classes/#using-liquid-classes))
@ecormany ecormany added docs DO NOT MERGE Indicates a PR should not be merged, even if there's a shiny green merge button available labels Jun 5, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

DO NOT MERGE Indicates a PR should not be merged, even if there's a shiny green merge button available docs

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants