Skip to content

Conversation

@emilyburghardt
Copy link
Collaborator

Overview

Adding a simple text blurb for PD 8.6.2 release notes, with no specific mention of Sentry use.

Test Plan and Hands on Testing

Changelog

Review requests

Risk assessment

low.

@codecov
Copy link

codecov bot commented Oct 28, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 25.26%. Comparing base (9faa319) to head (cd7fb01).
⚠️ Report is 9 commits behind head on edge.

Additional details and impacted files

Impacted file tree graph

@@            Coverage Diff             @@
##             edge   #19951      +/-   ##
==========================================
+ Coverage   25.20%   25.26%   +0.06%     
==========================================
  Files        3528     3531       +3     
  Lines      294549   295231     +682     
  Branches    39559    39720     +161     
==========================================
+ Hits        74240    74597     +357     
- Misses     220286   220611     +325     
  Partials       23       23              
Flag Coverage Δ
protocol-designer 18.77% <ø> (+0.01%) ⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.
see 23 files with indirect coverage changes

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

Copy link
Contributor

@alexjoel42 alexjoel42 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Amazing!

### Bug Fixes

- Crashes and protocol loss no longer occur when:
- Crashes and protocol loss no longer occur when:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is not new, but somehow this line got duplicated it. We can fix it along with whatever's making prettier mad.

@emilyburghardt emilyburghardt merged commit 4cd4ab9 into edge Oct 30, 2025
16 checks passed
@emilyburghardt emilyburghardt deleted the notes-PD-8.6.2 branch October 30, 2025 16:23
koji pushed a commit that referenced this pull request Nov 3, 2025
<!--
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

Adding a simple text blurb for PD 8.6.2 release notes, with no specific
mention of Sentry use.

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

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

## Changelog

<!--
List changes introduced by this PR considering future developers and the
end user. Give careful thought and clear documentation to breaking
changes.
-->

## Review requests

<!--
- What do you need from reviewers to feel confident this PR is ready to
merge?
- Ask questions.
-->

## Risk assessment

low. 

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

---------

Co-authored-by: Jamey Huffnagle <[email protected]>
Co-authored-by: Edward Cormany <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants