-
Notifications
You must be signed in to change notification settings - Fork 3.4k
chore: release 13.7.0 #29123
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore: release 13.7.0 #29123
Conversation
Co-authored-by: Matt Schile <[email protected]>
1 flaky test on run #54496 ↗︎Details:
|
Test | Artifacts | |
---|---|---|
... > can skip setup CT testing for an E2E project |
Test Replay
Screenshots
|
Review all test suite changes for PR #29123 ↗︎
This comment was marked as resolved.
This comment was marked as resolved.
"devDependencies": { | ||
"cross-env": "6.0.3", | ||
"cypress-example-kitchensink": "2.0.2", | ||
"cypress-example-kitchensink": "2.0.3", |
This comment was marked as resolved.
This comment was marked as resolved.
Sorry, something went wrong.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- This issue has been sorted out by chore: Update v8 snapshot cache #29128 which updated
yarn.lock
**Performance:** | ||
|
||
- Fixed a performance regression from [`13.6.4`](https://docs.cypress.io/guides/references/changelog#13-6-4) where unhandled service worker requests may not correlate correctly. Fixes [#28868](https://github.com/cypress-io/cypress/issues/28868). | ||
- Fixed a performance regression from [`13.6.3`](https://docs.cypress.io/guides/references/changelog#13-6-3) where unhandled service worker requests may not correlate correctly. Fixes [#28868](https://github.com/cypress-io/cypress/issues/28868). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@mschile regarding #29123 (comment), i'm confused, wasn't the performance regression reintroduced in 13.6.4 (and introduced the first time in 13.6.1)? From what I've tested, 13.6.1 super slow, then 13.6.3 works fine and from 13.6.4 on it doubles the time for network responses in my tests (slow again).
13.6.0 ✅
13.6.1 ❌
13.6.2 ❌
13.6.3 ✅
13.6.4 ❌
13.6.5 ❌
13.6.6 ❌
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@gabrielbahniuk, not that we are aware of. Can you try the pre-release binary (or wait until 13.7.0 is released) to see if it resolves your performance issue:
npm install https://cdn.cypress.io/beta/npm/13.7.0/linux-x64/develop-f8f7e71907870a50784a1a8547940902362b58e2/cypress.tgz
If your performance issue is not resolved, could you please open a new issue with a reproducible example so we can investigate.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@mschile sure, will do and reply here, but it's weird bc I tested multiple times and everything points to a fix in 13.6.3 (that's the version I'm using right now, as 13.6.4 also didn't work).
Released in This comment thread has been locked. If you are still experiencing this issue after upgrading to |
Additional details
Steps to test
How has the user experience changed?
PR Tasks
cypress-documentation
?type definitions
?