Opentrons

The 5.0.2 hotfix release contains three fixes in the Opentrons App:

1. If you use `load_labware_from_definition` in your Python protocol, you are now able to use Labware Position Check.
2. User-defined labware labels, if present, are now displayed in "Labware Setup"
3. Certain types of protocol upload failures will now show an error message instead of silently failing.

As well as three related fixes in the robot software:

1. The robot now understands how to use labware loaded via `load_labware_from_definition` during Labware Position Check.
2. User-defined labware labels are now returned to the Opentrons App from protocol analyses and runs.
3. Protocol file uploads now permit uppercase .json and .py extensions.

The 5.0.1 hotfix release contains a small fix to the Labware Position Check to appropriately handle protocols that load pipettes, but never pick up tips with that pipette.

Known Issues

Your last run protocol will not be saved through robot reboots

Version 4.7.0 of the Opentrons App and OT-2 Software is a release focused on stability and behind-the-scenes improvements to our software.

[Technical change log](https://github.com/Opentrons/opentrons/blob/edge/CHANGELOG.md)

Opentrons App

There are no Opentrons App changes for this release.

OT-2 Software

Bug Fixes

- [feat(api,robot-server): upgrade fastapi and pydantic deps ](https://opentrons.atlassian.net/wiki/spaces/RPDO/pages/1041432676/4.7.x+Internal+Release+Notes#Feat(api,robot-server):-upgrade-fastapi-and-pydantic-deps)
- [fix(api): thermocycler error handling ](https://opentrons.atlassian.net/wiki/spaces/RPDO/pages/1041432676/4.7.x+Internal+Release+Notes#Fix(api):-thermocycler-error-handling)
- [revert(robot-server): revert attach pipette code back to using the mount](https://opentrons.atlassian.net/wiki/spaces/RPDO/pages/1041432676/4.7.x+Internal+Release+Notes#revert(robot-server):-revert-attach-pipette-code-back-to-using-the-mount)
- [refactor(api): lock reads to pipettes in the hardware controller](https://opentrons.atlassian.net/wiki/spaces/RPDO/pages/1041432676/4.7.x+Internal+Release+Notes#refactor(api):-lock-reads-to-pipettes-in-the-hardware-controller-8639)
- [fix(robot-server): avoid LabwareDefinition type in cal models](https://opentrons.atlassian.net/wiki/spaces/RPDO/pages/1041432676/4.7.x+Internal+Release+Notes#fix(robot-server):-avoid-LabwareDefinition-type-in-cal-models-8698)

Version 4.6.2 of the Opentrons App and OT-2 Software is a release focused on stability and behind-the-scenes improvements to our software as well as a useful experimental command line utility.

[Technical change log](https://github.com/Opentrons/opentrons/blob/edge/CHANGELOG.md#461-2021-09-28)

Opentrons App

This is a quiet release on the app front as we make some behind-the-scenes improvements to how the app is built, so we don't have any changes to report here.

OT-2 Software

New Features

- The `opentrons_simulate` command-line application can now estimate protocol duration using the `-e` option. This feature is experimental, but very cool!

Bug Fixes

- If a protocol is canceled mid-run while there is a tip on a pipette, the tip will be dropped prior to resetting the plunger to avoid contaminating the pipette internals with liquids.
- Fixed a movement planning issue that could cause multi-channel pipettes to collide with the deck when changing pipettes.
- Fixed an issue that could cause the protocol to proceed before an awaited temperature module target was actually hit.
- Fixed a few issues with the faster protocol analysis method added in the 4.5.0 release.
- Fixed type annotations of the `ProtocolContext` classes.

The 4.6.2 hotfix release contains a small bug fix for an issue where the OT-2's max speed settings within a protocol will be ignored.

The 4.6.1 hotfix release contains a small configuration change to fix an issue with installing the `opentrons` PyPI package on computers running Python 3.8 and later. It does not affect the software running on your OT-2.

Known Issues

In 4.6.2 and previous releases, the OT-2 will only use TLS 1.0 for WPA2 Enterprise association. Some RADIUS servers have disabled this version of TLS; it must be enabled to connect the OT-2 to a RADIUS-secured network.

Since version 4.5.0, if a thermocycler encounters an error, the robot will be unable to recognize the error state. If your thermocycler starts blinking its yellow LED, you should cancel your protocol. See issue [8393][] for more details.

[8393]: https://github.com/Opentrons/opentrons/issues/8393