You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
feat: exit with code 112 when api errors prevent cloud orchestrated runs (record mode, parallel run mode) (#32635)
* feat: exit with code 112 on fatal api errors when posix error codes are enabled
* rm dead code
* ts
* system tests for 112 exit code
* fix race condition w/ exit codes
* only 112 on network errors, not http errors
* have connection timeouts run a little bit faster in system tests
* new schema for network errors
* 112 should only be on network errors, update integration test
* changelog
* changelog
* coerce boolean
* code review
* review
* rm extra debug
Copy file name to clipboardExpand all lines: cli/CHANGELOG.md
+5-1Lines changed: 5 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,8 +1,12 @@
1
1
<!-- See the ../guides/writing-the-cypress-changelog.md for details on writing the changelog. -->
2
-
## 15.4.1
2
+
## 15.5.0
3
3
4
4
_Released 10/21/2025 (PENDING)_
5
5
6
+
**Features:**
7
+
8
+
- When `cypress run` is used with both `--record` and `--posix-exit-codes` enabled, Cypress will now exit with code `112` when it cannot determine which spec to run next due to network conditions. Addresses [#32485](https://github.com/cypress-io/cypress/issues/32485). Addressed in [#32635](https://github.com/cypress-io/cypress/pull/32635).
9
+
6
10
**Bugfixes:**
7
11
8
12
- An error is no longer thrown during command execution when the application under test overwrites the `window.$` property with a non-function. Fixes [#1502](https://github.com/cypress-io/cypress/issues/1502). Fixed in [#32682](https://github.com/cypress-io/cypress/pull/32682).
0 commit comments