Skip to content

docs: robot stack 9.1.0#21677

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

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

Conversation

@ecormany

@ecormany ecormany commented Jun 5, 2026

Copy link
Copy Markdown
Contributor

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.

@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
@ecormany ecormany force-pushed the docs-release-9.1.0 branch from 040d90a to 8356121 Compare June 12, 2026 16:48
@ecormany ecormany requested review from a team as code owners June 12, 2026 16:48
@ecormany ecormany requested review from ncdiehl11 and removed request for a team June 12, 2026 16:48
@codecov

codecov Bot commented Jun 12, 2026

Copy link
Copy Markdown

Codecov Report

❌ Patch coverage is 22.72727% with 34 lines in your changes missing coverage. Please review.
✅ Project coverage is 21.30%. Comparing base (cc087d3) to head (8356121).
⚠️ Report is 135 commits behind head on edge.

Files with missing lines Patch % Lines
...otocolDetails/AnnotatedSteps/IndividualCommand.tsx 0.00% 21 Missing ⚠️
...ms/Desktop/ProtocolDetails/AnnotatedSteps/utils.ts 53.33% 5 Missing and 2 partials ⚠️
.../ProtocolDetails/AnnotatedSteps/AnnotatedGroup.tsx 33.33% 0 Missing and 2 partials ⚠️
...s/Desktop/ProtocolDetails/AnnotatedSteps/index.tsx 0.00% 2 Missing ⚠️
...ms/Desktop/Devices/PipetteCard/FlexPipetteCard.tsx 0.00% 0 Missing and 1 partial ⚠️
app/src/pages/ODD/ConnectViaUSB/index.tsx 50.00% 0 Missing and 1 partial ⚠️
Additional details and impacted files

Impacted file tree graph

@@           Coverage Diff           @@
##             edge   #21677   +/-   ##
=======================================
  Coverage   21.30%   21.30%           
=======================================
  Files        3912     3912           
  Lines      326847   326848    +1     
  Branches    58106    58104    -2     
=======================================
+ Hits        69629    69633    +4     
+ Misses     254228   254223    -5     
- Partials     2990     2992    +2     
Flag Coverage Δ
app 46.01% <22.72%> (-0.01%) ⬇️
step-generation 61.00% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Files with missing lines Coverage Δ
...rc/organisms/Desktop/Devices/GripperCard/index.tsx 18.64% <ø> (+0.10%) ⬆️
...on/src/organisms/AnnotatedSteps/AnnotatedGroup.tsx 0.00% <ø> (ø)
...src/organisms/AnnotatedSteps/IndividualCommand.tsx 0.00% <ø> (ø)
...sualization/src/organisms/AnnotatedSteps/index.tsx 0.00% <ø> (ø)
...r/maintenance_runs/maintenance_run_data_manager.py 78.68% <ø> (ø)
robot-server/robot_server/runs/run_data_manager.py 87.95% <ø> (ø)
...-data/python/opentrons_shared_data/errors/codes.py 94.62% <ø> (ø)
.../python/opentrons_shared_data/errors/exceptions.py 51.03% <ø> (ø)
...-server/system_server/service/check_jwt_headers.py 100.00% <ø> (ø)
...ms/Desktop/Devices/PipetteCard/FlexPipetteCard.tsx 19.74% <0.00%> (+0.16%) ⬆️
... and 5 more
🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@ecormany ecormany force-pushed the docs-release-9.1.0 branch 2 times, most recently from 3f9bb4d to 13479dd Compare June 12, 2026 17:17
jwwojak and others added 6 commits June 12, 2026 13:21
# 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))
Adding step grouping to the API docs for 2.29. Includes a screenshot
showing why this is useful in protocol visualization!

---------

Co-authored-by: Edward Cormany <edward.cormany@opentrons.com>
Additional updates to docs for API 2.29. Depends on PR #21556 (should be
merged first), and includes:

- breaking Liquid Classes into multiple articles collapsed into a single
section (we have a LOT of information here. there are a few links that
will need to be changed in the Flex manual and, this change is ticketed
[here](https://opentrons.atlassian.net/browse/RTC-1006)).
- unhiding `set_empty()` docs I wrote earlier (API 2.28) now that we
have a fix (previously, tip racks that were set as empty did not appear
as empty in deck setup and could have presented a collision risk).
- versioning page (trying out some new language for the OT-2 app)
- fix incorrect use of `set_for_volume` in liquid class custom code
example that [Sanniti
found](https://opentrons.atlassian.net/browse/AUTH-2902?focusedCommentId=153251&sourceType=mention)
@ecormany ecormany force-pushed the docs-release-9.1.0 branch from 9148817 to 91d7626 Compare June 12, 2026 17:22
ecormany and others added 2 commits June 12, 2026 13:29
# Overview

Change "Opentrons App" to "Opentrons OT-2 App" in the OT-2 manual. 

Swapped 1:1 except in any obvious cases where it might be obnoxious to
repeat it. Might be more of those lingering.

## Test Plan and Hands on Testing


## Changelog



## Review requests



## Risk assessment

low.
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