Cypress 16.2.1 Fixes Runs That Hang or Fail After Passing. What to Check Before You Upgrade

Cypress 16.2.1 fixes cross-origin hangs on large specs, stalls after hook timeouts, exit code 1 on all-green runs, and false Modified tests in Cloud. It also changes TLS checks in Node code.
Quick answer
Cypress 16.2.1 (October 28, 2026) fixes specs above about 75 MB hanging at their first cross-origin cy.visit() in Chromium browsers, cypress run stalling after a retried hook timeout, all-pass runs exiting with code 1, and Cypress Cloud marking unchanged tests as Modified when Test Replay switches browsers. Node code in setupNodeEvents and cy.task() now verifies TLS like Node, so check calls to self-signed hosts.
Key takeaways
- Cypress 16.2.1 was released on October 28, 2026 to fix runs that hang or fail after passing.
- Large specs (about 75 MB+) no longer hang at the first cross-origin cy.visit() in Chrome, Chromium, and Edge.
- All-pass runs no longer exit with code 1, so remove any exit-code workarounds after upgrading.
- setupNodeEvents and cy.task() now verify TLS certificates like Node does. Check HTTPS calls to self-signed hosts.
- Upgrade on a branch, run the suite in CI several times, and compare against saved example runs.
Some CI failures are easy. A test breaks, you read the error, you fix it.
Then there are the other kind. The run sits there and never finishes. Or every test passes and the job still goes red. Or Cypress Cloud flags a pile of tests as Modified when nobody touched them. These are the ones that eat a whole afternoon, because the problem isn't in your tests at all.
Cypress 16.2.1, released on October 28, 2026, is aimed squarely at that second kind. Cypress describes it as "fixes for runs that hang or fail after passing." If your team has been chasing ghosts in CI, this is worth a careful look.
Below is what changed, how to tell if it affects you, and what to check before and after you upgrade.
The five fixes, in plain words
Going straight from the release notes:
- Large specs hanging on cross-origin visits. In Chrome, Chromium, and Edge, specs bundled above about 75 MB no longer hang at their first
cy.visit()to another origin. - Stalls after a hook timeout.
cypress runno longer stalls when a test retries after a hook timed out. - Exit code 1 on a clean run. A run where every test passed no longer exits with code 1.
- False "Modified" tests in Cypress Cloud. Cloud no longer lists unchanged tests as Modified when a Test Replay run switches browsers.
- TLS checks in Node code. Node code in
setupNodeEventsandcy.task()now verifies TLS certificates the same way Node does.
The first four are pure bug fixes. The fifth is a behavior change, and it's the one that can surprise you after upgrading. More on that below.
How to tell if you've been hit
Before you upgrade, it helps to know which of these you were actually seeing. That way you can confirm the fix instead of just hoping.
Hanging at the first cross-origin visit. Look for runs that freeze right when a spec calls cy.visit() on a different origin, often a login or payment page on another domain. Then check your bundle size. If a spec pulls in a lot of fixtures, big libraries, or generated data, its bundle can get large. The release notes put the line at about 75 MB, and only in Chromium-family browsers.
Stalls after a hook timeout. Check your logs for a before or beforeEach hook that timed out, followed by a retry, followed by nothing. If you have test retries turned on and a flaky setup hook, this pattern fits.
Green run, red job. This one is easy to spot. Every test shows as passed in the output, but the process exits with code 1 and your pipeline marks the build as failed. If your team has been adding || true or rerun steps to get around it, now is the time to look again.
Phantom "Modified" tests. If you use Test Replay and run across more than one browser, check whether Cloud has been marking tests as Modified when the code didn't change. This can mess with any reporting or flake tracking you build on top of Cloud.
The TLS change is the one to plan for
Here is the exact line from Cypress: Node code in setupNodeEvents and cy.task() "now verifies TLS certificates the same way Node does, so check any HTTPS calls to self-signed hosts when you upgrade."
What this means in practice: if your config or tasks call out to HTTPS services, those calls now get the normal Node certificate checks. A lot of test setups talk to internal services with self-signed certs, like a staging API, a local mock server, or a seed-data endpoint. Those calls may have worked before and could start failing now.
Things to search your repo for:
setupNodeEventsblocks that make HTTP requests.cy.task()handlers that hit an API to seed or reset data.- Any helper that talks to a staging or dev host over HTTPS.
If you find self-signed hosts, the right fix is to give Node the proper CA certificate for those hosts, not to switch off verification across the board. Turning off TLS checks globally in test code has a way of sneaking into other places.
A simple upgrade plan
You don't need a big project for a patch release. But because one of the fixes changes behavior, a short plan helps.
Before you upgrade
- Write down which of the five symptoms you've seen, with a link to one example run for each. You'll use these to confirm the fix.
- List every place your Node-side code (
setupNodeEvents,cy.task()) makes HTTPS calls, and note which hosts use self-signed certs. - Find any workarounds your team added for these bugs: forced exit codes, extra rerun steps, skipped specs, browser pinning. Mark them so you remember to remove them.
Upgrade on a branch first
- Bump Cypress to 16.2.1 on a branch and run the full suite in CI as well as locally. Hangs like these can depend on the CI machine, so a clean local run may not tell you much.
- Run it more than once. Hangs and stalls are often intermittent, so one clean run doesn't prove much.
- Watch the
cy.task()and config steps closely for new TLS errors.
After you upgrade
- Re-run the example builds you saved and compare.
- Remove the workarounds you marked earlier, one at a time. A forced
exit 0that hides real failures is worse than the bug it was covering. - If you use Cypress Cloud with Test Replay across browsers, check that the Modified count looks sane on the next few runs.
Why this matters more than a typical patch
A run that hangs costs you CI minutes. A run that fails after passing costs you something bigger: trust in the pipeline.
When people see red builds with all-green tests a few times, they stop believing the signal. They start clicking rerun without reading. They merge on a red build because "it's always like that." That habit is how real failures slip through.
So even if you've only hit one of these bugs once or twice, it's worth upgrading and cleaning up the workarounds. A pipeline that's green when tests pass and red when they fail is the whole point.
Quick checklist
- Note which symptoms you've seen, with example runs
- Find Node-side HTTPS calls in
setupNodeEventsandcy.task() - Sort out certs for any self-signed hosts
- Upgrade to 16.2.1 on a branch, run the suite in CI a few times
- Confirm the old example runs now behave
- Remove exit-code hacks and other workarounds
- Check Cloud's Modified count if you use Test Replay
Full details are in the Cypress 16.2.1 release notes.
Frequently asked questions
It fixes large specs hanging on their first cross-origin cy.visit() in Chromium browsers, cypress run stalling after a hook timeout retry, all-pass runs exiting with code 1, and Cypress Cloud showing unchanged tests as Modified when Test Replay switches browsers.


