Skip to content

fix: ensure that fatal protocol errors are only limited to the spec they occurred on - #27720

Merged
ryanthemanuel merged 4 commits into
developfrom
ryanm/fix/fatal-protocol-errors-limited-to-spec
Aug 31, 2023
Merged

ryanthemanuel merged 4 commits into
developfrom
ryanm/fix/fatal-protocol-errors-limited-to-spec

Conversation

@ryanthemanuel

Copy link
Copy Markdown
Collaborator

Additional details

Ensure that protocol errors are only limited to the spec they occurred on. Previously fatal errors would leak over from spec to spec.

How has the user experience changed?

n/a

PR Tasks

@ryanthemanuel
ryanthemanuel requested a review from mjhenkes August 31, 2023 14:47
@cypress

cypress Bot commented Aug 31, 2023 •

Copy link
Copy Markdown

@ryanthemanuel
ryanthemanuel merged commit d8b4821 into develop Aug 31, 2023
@ryanthemanuel
ryanthemanuel deleted the ryanm/fix/fatal-protocol-errors-limited-to-spec branch August 31, 2023 16:01
@cypress-bot

cypress-bot Bot commented Aug 31, 2023

Copy link
Copy Markdown
Contributor

Released in 13.1.0.

This comment thread has been locked. If you are still experiencing this issue after upgrading to
Cypress v13.1.0, please open a new issue.

@cypress-bot cypress-bot Bot locked as resolved and limited conversation to collaborators Aug 31, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants