Cypress 16.2.1 Addresses Hanging Runs, Oversized Specs, and Command Regressions
Cypress 16.2.1 improves CI reliability by fixing hangs on cross-origin visits from oversized specs, stalled retries, slow test-isolation startup, and several command failures.
Cypress 16.2.1 is a maintenance release for teams whose runs hang, return the wrong exit code, or fail in cases that are hard to reproduce locally. Released on October 28, 2026, the patch is available through the Cypress npm package and focuses on reliability rather than new test-authoring features. ([docs.cypress.io](https://docs.cypress.io/app/references/changelog?utm_source=openai))
The largest fix concerns browser bundles. In Cypress 16.0.0, a Chrome, Chromium, or Edge spec could hang indefinitely on its first cy.visit() to another origin when the bundled file exceeded roughly 75 MB. The run never reached the configured pageLoadTimeout, forcing teams to terminate cypress run themselves. Cypress 16.2.1 fixes the regression, and the release notes say the forceHttp1 workaround is no longer needed for this case. ([docs.cypress.io](https://docs.cypress.io/app/references/changelog?utm_source=openai))
What changed in Cypress 16.2.1
- Large cross-origin specs no longer hang on the first visit. This is most relevant to generated front-end code, large application bundles, and suites that import substantial helper libraries.
- Retries after hook timeouts no longer stall the run. The release announcement identifies a case in which
cypress runstopped progressing after a test retried following a hook timeout. ([cypress.io](https://www.cypress.io/releases/16-2-1?utm_source=openai)) - Passing runs now exit successfully. Cypress fixed a condition that could give a fully passing run exit code 1, causing CI to report a failure without any failed assertion to investigate. ([cypress.io](https://www.cypress.io/releases/16-2-1?utm_source=openai))
- Test isolation starts faster in some API-heavy cases. If the previous test did not load a page, such as one that only used
cy.request(), Cypress can skip unnecessary startup work. ([docs.cypress.io](https://docs.cypress.io/app/references/changelog?utm_source=openai)) - Several command and browser regressions are fixed. The list includes
cy.contains()insidecy.document().within(), decodingx-gzipresponses when Cypress rewrites them, invalid encoding values passed tocy.request(), scroll positions that stopped short, and a headed-browser extension regression affecting Chrome, Chromium, and Edge. ([docs.cypress.io](https://docs.cypress.io/app/references/changelog?utm_source=openai))
What QA teams should test before upgrading
Start with the CI paths these fixes affect. Run specs with large generated bundles and at least one cross-origin navigation in Chrome or Chromium. If the pipeline set forceHttp1: true solely to prevent a hanging visit, compare a run without that workaround and keep the change isolated so any failure is easy to trace.
Then exercise retries around beforeEach, afterEach, and other hooks that can time out. Check both the final test result and the process exit code. A passing report paired with exit code 1 can block a deployment without pointing to a test assertion, so add a direct CI check for it.
Teams running API-only or mixed API and browser specs should compare startup time and isolation behavior across a representative run. The change should show up when a test uses commands such as cy.request() without loading a page, but it should not alter assumptions about cookies, storage, or session setup.
Should you upgrade?
Cypress 16.2.1 is a worthwhile patch upgrade for projects already on Cypress 16, particularly when CI runs include oversized specs, hook retries, cross-origin navigation, or unexplained exit-code failures. It does not require a test rewrite, but teams should still run their browser matrix and review custom workarounds added after Cypress 16.0.0.
For teams on an earlier major version, the decision is broader because Cypress 16 introduced larger platform and behavior changes. Use 16.2.1 as the patch target for a planned major-version migration, not as a replacement for reviewing the full Cypress 16 migration guidance.
Looking for tools to match this read?
Jump into our independent side-by-side comparisons.
More in Tool Updates
.NET 11 Released: What QA Teams Need to Check in the New dotnet test
.NET 11 adds run-level test policies, clearer CI output, mobile test support, traversal projects, and new Microsoft.Testing.Platform options. QA teams should test these changes before upgrading.
GitHub Actions Secret Scanning Now Checks Workflow Logs: What QA Teams Need to Know
GitHub's public preview scans completed Actions workflow logs for leaked credentials. QA teams need to understand what it covers, how to enable it, and where it falls short before relying on it instead of disciplined test-pipeline hygiene.
SonarQube CLI 1.12.0 Adds Architecture Findings, Secret Redaction, and Simpler Project Administration
SonarQube CLI 1.12.0 adds architecture findings for SonarQube Cloud, redacts secrets in selected AI-agent workflows, and simplifies repository imports, project linking, and authentication management.