Skip to content

Commit

Permalink
chore: release notes for 0.12.0
Browse files Browse the repository at this point in the history
  • Loading branch information
sfoster1 committed Jun 13, 2023
1 parent 1624e48 commit 8403afb
Show file tree
Hide file tree
Showing 2 changed files with 14 additions and 16 deletions.
19 changes: 8 additions & 11 deletions api/release-notes-internal.md
Original file line number Diff line number Diff line change
Expand Up @@ -6,19 +6,11 @@ For more details about this release, please see the full [technical change log][

# Internal Release 0.12.0

## New Stuff In This Release
## Update Notes

- If your Python protocol specifies a Flex-style slot name like `"C2"`, its `apiLevel` must now be `2.15`.

# Internal Release 0.11.0

This is internal release 0.11.0 for the Opentrons Flex robot software, involving both robot control and the on-device display.

Some things are known not to work, and are listed below. Specific compatibility notes about peripheral hardware are also listed.

## Update Notes

- ⚠️ After upgrading your robot to 0.11.0, you'll need to factory-reset its run history before you can use it.
- ⚠️ After upgrading your robot to 0.12.0 from 0.10.0 or previous, you'll need to factory-reset its run history before you can use it.

1. From the robot's 3-dot menu (⋮), go to **Robot settings.**
2. Under **Advanced > Factory reset**, select **Choose reset settings.**
Expand All @@ -30,7 +22,12 @@ Some things are known not to work, and are listed below. Specific compatibility

## New Stuff In This Release

- The HTTP API will now accept both styles of deck slot name: coordinates like "C2", and integers like "5". Flexes will now return the "C2" style, and OT-2s will continue to return the "5" style.
- Many (many) visual and workflow fixes and improvements from design QA for the ODD
- Pipette plunger backlash compensation should improve pipetting performance on the 96 channel
- More slot name fixes to make them D1 instead of 1
- 96 channel attach flow fixes
- Firmware updates now use an HTTP API; there's no frontend, so continue to follow the rules abotu restarting with an instrument attached after an update.
- Several ODD white screen fixes

## Big Things That Don't Work Yet So Don't Report Bugs About Them

Expand Down
11 changes: 6 additions & 5 deletions app-shell/build/release-notes-internal.md
Original file line number Diff line number Diff line change
Expand Up @@ -3,15 +3,15 @@ For more details about this release, please see the full [technical changelog][]

---

# Internal Release 0.11.0
# Internal Release 0.12.0

This is 0.11.0, an internal release for the app supporting the Opentrons Flex.
This is 0.12.0, an internal release for the app supporting the Opentrons Flex.

This is still pretty early in the process, so some things are known not to work, and are listed below. Some things that may surprise you do work, and are also listed below. There may also be some littler things of note, and those are at the bottom.

## Update Notes

- ⚠️ After upgrading your robot to 0.11.0, you'll need to factory-reset its run history before you can use it.
- ⚠️ After upgrading your robot to 0.12.0 from 0.10.0 or previous, you'll need to factory-reset its run history before you can use it.

1. From the robot's 3-dot menu (⋮), go to **Robot settings.**
2. Under **Advanced > Factory reset**, select **Choose reset settings.**
Expand All @@ -24,9 +24,10 @@ This is still pretty early in the process, so some things are known not to work,
- After upgrading your app, the protocols that you already had imported to the app will display blank deck maps. To fix this, select **Reanalyze** from the protocol's 3-dot menu (⋮).

## New Stuff In This Release
- You can disable the LED bar at the top now!
- Attach flow updates and fixes for 96 channel
- Many (many) visual and workflow fixes and improvements from design QA for the app

- When interacting with an OT-3, the app will use the newer names for the deck slots, like "C2", instead of the names from the OT-2, like "5".
- The `requirements` dict in Python protocols can now have `"robotType": "Flex"` instead of `"robotType": "OT-3"`. `"OT-3"` will still work, but it's discouraged because it's not the customer-facing name.

## Big Things That Don't Work Yet So Don't Report Bugs About Them
- Attach, detach, and calibration flows for anything from the protocol setup page
Expand Down

0 comments on commit 8403afb

Please sign in to comment.