additional 2.29 docs changes#21489
Draft
emilyburghardt wants to merge 5 commits into
Draft
Conversation
ecormany
reviewed
May 20, 2026
| @@ -60,14 +60,15 @@ If you upload a protocol that specifies a higher API level than the maximum supp | |||
| Opentrons robots running the latest software ({{ robot_stack_version }}) support the following version ranges: | |||
Contributor
There was a problem hiding this comment.
This sentence needs an update because it talks about a single app.
Collaborator
Author
There was a problem hiding this comment.
Added in some language earlier to specify that there's different apps and software versions. See what you think.
The way it was earlier felt to me a bit like the software split was being hidden from users. I don't need to hammer this home here, but I feel like it should get a mention.
emilyburghardt
force-pushed
the
docs-additional-api-2.29
branch
from
2465131 to
b929a03
Compare
emilyburghardt
changed the base branch from
docs-release-9.1.0
to
chore_release-9.1.0
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## chore_release-9.1.0 #21489 +/- ##
====================================================
Coverage 21.70% 21.70%
====================================================
Files 3911 3911
Lines 327234 327234
Branches 58192 58195 +3
====================================================
Hits 71041 71041
Misses 253222 253222
Partials 2971 2971
Flags with carried forward coverage won't be shown. Click here to find out more. 🚀 New features to boost your workflow:
|
emilyburghardt
temporarily deployed
to
pd-non-prod
GitHub Actions
Inactive
emilyburghardt
added
the
DO NOT MERGE
emilyburghardt
force-pushed
the
docs-additional-api-2.29
branch
2 times, most recently
from
b55fe80 to
986757d
Compare
emilyburghardt
added a commit
that referenced
this pull request
Jun 4, 2026
# 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
force-pushed
the
docs-additional-api-2.29
branch
from
986757d to
690cafd
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Overview
Additional updates to docs for API 2.29. Depends on PR #21556 (should be merged first), and includes:
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).set_for_volumein liquid class custom code example that Sanniti foundTest Plan and Hands on Testing
sandbox (once it builds)
Changelog
Review requests
I've checked all the links in the updated liquid class articles, but a second set of eyes can't hurt.
Risk assessment
low.