You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
<!--
Thanks for taking the time to open a Pull Request (PR)! Please make sure
you've read the "Opening Pull Requests" section of our Contributing
Guide:
https://github.com/Opentrons/opentrons/blob/edge/CONTRIBUTING.md#opening-pull-requests
GitHub provides robust markdown to format your PR. Links, diagrams,
pictures, and videos along with text formatting make it possible to
create a rich and informative PR. For more information on GitHub
markdown, see:
https://docs.github.com/en/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax
To ensure your code is reviewed quickly and thoroughly, please fill out
the sections below to the best of your ability!
-->
# Overview
<!--
Describe your PR at a high level. State acceptance criteria and how this
PR fits into other work. Link issues, PRs, and other relevant resources.
-->
Adding API 2.22 to our PAPI versioning page. Now, we document API 2.22
for customers, but it's clear that this version only contains changes
for our commercial partners.
## Test Plan and Hands on Testing
<!--
Describe your testing of the PR. Emphasize testing not reflected in the
code. Attach protocols, logs, screenshots and any other assets that
support your testing.
-->
Needs to be built
## Changelog
<!--
List changes introduced by this PR considering future developers and the
end user. Give careful thought and clear documentation to breaking
changes.
-->
-update versions table
-add a simple version description for API 2.22
## Review requests
<!--
- What do you need from reviewers to feel confident this PR is ready to
merge?
- Ask questions.
-->
## Risk assessment
<!--
- Indicate the level of attention this PR needs.
- Provide context to guide reviewers.
- Discuss trade-offs, coupling, and side effects.
- Look for the possibility, even if you think it's small, that your
change may affect some other part of the system.
- For instance, changing return tip behavior may also change the
behavior of labware calibration.
- How do your unit tests and on hands on testing mitigate this PR's
risks and the risk of future regressions?
- Especially in high risk PRs, explain how you know your testing is
enough.
-->
low
Copy file name to clipboardexpand all lines: api/docs/v2/versioning.rst
+6
Original file line number
Diff line number
Diff line change
@@ -84,6 +84,8 @@ This table lists the correspondence between Protocol API versions and robot soft
84
84
+-------------+------------------------------+
85
85
| API Version | Introduced in Robot Software |
86
86
+=============+==============================+
87
+
| 2.22 | 8.3.0 |
88
+
+-------------+------------------------------+
87
89
| 2.21 | 8.2.0 |
88
90
+-------------+------------------------------+
89
91
| 2.20 | 8.0.0 |
@@ -136,6 +138,10 @@ This table lists the correspondence between Protocol API versions and robot soft
136
138
Changes in API Versions
137
139
=======================
138
140
141
+
Version 2.22
142
+
-------------
143
+
This version includes beta features for our commercial partners.
144
+
139
145
Version 2.21
140
146
------------
141
147
- Adds :py:class:`.AbsorbanceReaderContext` to support the :ref:`Absorbance Plate Reader Module <absorbance-plate-reader-module>`. Use the load name ``absorbanceReaderV1`` with :py:meth:`.ProtocolContext.load_module` to add an Absorbance Plate Reader to a protocol.
0 commit comments