breaking: update execa from 1.0.0 to 4.1.0

[AtofStryker]

• Closes N/A

Additional details

Updating execa from 1.0.0 to 4.x in the data-context and server packages, 1.0.0 was released on Nov 12, 2018.

The main breaking changes relevant to us:

• Remove execa.shell() and execa.shellSync(). The shell option should be used instead. (Remove execa.shell() and execa.shellSync() sindresorhus/execa#219)
• Remove error.code (number or string) in favor of error.exitCode (number) and error.exitCodeName (string) (Distinguishing between error strings and error numbers sindresorhus/execa#187, Remove error.code sindresorhus/execa#250)

Some of this code in the data-context package likely never functioned correctly. This exitCode does not exist on 1.0.0 of execa, it was added in 2.0.0, so I think this code path would never have run.

Also, since code changed to exitCode, this would be a breaking change to cy.exec() as the results object is now different.

Steps to test

How has the user experience changed?

PR Tasks

• Have tests been added/updated?
• Has a PR for user-facing changes been opened in cypress-documentation? chore: update code to exitCode in cy.exec() cypress-documentation#6247 feat: add cy.exec() Cypress 15 misc test compatibility cypress-example-kitchensink#984
• Have API changes been updated in the type definitions?

[cypress]

cypress    Run #64719

Run Properties:   Failed #64719  •  82c4726f1c: Update cli/CHANGELOG.md

Project	cypress
Branch Review	breaking/update_execa
Run status	Failed #64719
Run duration	18m 07s
Commit	82c4726f1c: Update cli/CHANGELOG.md
Committer	Jennifer Shehane
View all properties for this run ↗︎

---

Test results
Failures	1
Flaky	2
Pending	28
Skipped	0
Passing	787
View all changes introduced in this branch ↗︎

UI Coverage  61.84%
Untested elements	27
Tested elements	47

Accessibility  99%
Failed rules	0 critical   3 serious   1 moderate   0 minor
Failed elements	19

---

Tests for review

  cypress\e2e\config-warning.cy.ts • 1 failed test • launchpad-e2e

View Output

Test		Artifacts
component testing dependency warnings > does not show warning for project that does not require bundler to be installed		Test Replay Screenshots

  cypress\e2e\cypress-origin-communicator.cy.ts • 1 flaky test • app-e2e

View Output

Test		Artifacts
Cypress In Cypress Origin Communicator > primary origin memory leak prevention > cleans up the primaryOriginCommunicator events when navigating away from the /specs to /runs		Test Replay Screenshots

  cypress\e2e\specs_list_actual_git_repo.cy.ts • 1 flaky test • app-e2e

View Output

Test		Artifacts
Spec List - Last updated with git info > shows correct git icons		Test Replay Screenshots

[MikeMcC399]

• feat: add cy.exec() Cypress 15 misc test compatibility cypress-example-kitchensink#984 created to allow scaffolded tests using cy.exec() to succeed in Cypress 14 and Cypress 15, and for this to be pulled into Cypress develop for CI tests
• test: Cypress 15 test-project preparation cypress-docker-images#1397 created to also allow the test-project in the Docker repo to succeed now and during the release of Cypress 15

[MikeMcC399]

@AtofStryker

cypress-io/cypress-example-kitchensink#984 has been merged and so now [email protected] has been released and the npm registry is showing it as published:

$ npm view cypress-example-kitchensink dist-tags
{ dev: '0.8.0', latest: '5.1.0' }

It probably makes sense to bump cypress-example-kitchensink to 5.1.0 in packages/example/package.json in this PR, so that the changes are synchronized.

[MikeMcC399]

@AtofStryker

It looks like you're running CircleCI against your closed PR

• breaking: add changes needed for release 15 cypress-example-kitchensink#983 instead of
• feat: add cy.exec() Cypress 15 misc test compatibility cypress-example-kitchensink#984

Probably you'll need to bump that one ... to test it properly against what is published.

[AtofStryker]

@AtofStryker

It looks like you're running CircleCI against your closed PR

• breaking: add changes needed for release 15 cypress-example-kitchensink#983 instead of
• feat: add cy.exec() Cypress 15 misc test compatibility cypress-example-kitchensink#984

Probably you'll need to bump that one ... to test it properly against what is published.

ah thanks for reminding me! Going to make sure the windows jobs pass first

[AtofStryker]

the non kitchensink ones obviously 😂

[MikeMcC399]

@AtofStryker

Hopefully you'll be able to get the Windows tests running soon. If not, then I'd suggest putting in an interim PR which ties the kitchensink tests back to an earlier PR cypress-io/cypress-example-kitchensink#978 before the misc.cy.js was updated to be compatible with this PR. Currently all open PRs in this repo are failing kitchensink tests.

[AtofStryker]

@MikeMcC399 the windows build are passing. Currently fixing a broken launchpad test which should now be passing. This likely will be merged in today

[MikeMcC399]

@AtofStryker

I'd like to test the cy..exec() change using a Cypress pre-release in the Cypress Docker build process, however I'm getting a 404 on the binary for:

npm install https://cdn.cypress.io/beta/npm/15.0.0/linux-x64/develop-f6e0744e38f6b86af49ea3b036bedbe45a672008/cypress.tgz

npm error URL: https://cdn.cypress.io/beta/binary/15.0.0/linux-x64/develop-f6e0744e38f6b86af49ea3b036bedbe45a672008/cypress.zip
npm error Error: Failed downloading the Cypress binary.
npm error Response code: 404
npm error Response message: Not Found

Can you recommend a working linux-x64 pre-release I can use, or perhaps purge the Cloudflare cache?

[AtofStryker]

@AtofStryker

I'd like to test the cy..exec() change using a Cypress pre-release in the Cypress Docker build process, however I'm getting a 404 on the binary for:

npm install https://cdn.cypress.io/beta/npm/15.0.0/linux-x64/develop-f6e0744e38f6b86af49ea3b036bedbe45a672008/cypress.tgz

npm error URL: https://cdn.cypress.io/beta/binary/15.0.0/linux-x64/develop-f6e0744e38f6b86af49ea3b036bedbe45a672008/cypress.zip
npm error Error: Failed downloading the Cypress binary.
npm error Response code: 404
npm error Response message: Not Found

Can you recommend a working linux-x64 pre-release I can use, or perhaps purge the Cloudflare cache?

@MikeMcC399 is the binary still 404ing for you?

[MikeMcC399]

@AtofStryker

is the binary still 404ing for you?

Unfortunately yes. This issue also cropped up during the 14.5.3 release (non beta binary).

Cloudflare cache believes the file doesn't exist, but if I bust the cache by appending an arbitrary query to the URL then it is able to find the zip file.

$ curl -I https://cdn.cypress.io/beta/binary/15.0.0/linux-x64/develop-f6e0744e38f6b86af49ea3b036bedbe45a672008/cypress.zip

curl -I https://cdn.cypress.io/beta/binary/15.0.0/linux-x64/develop-f6e0744e38f6b86af49ea3b036bedbe45a672008/cypress.zip?cache_bust=0
HTTP/2 404
date: Tue, 19 Aug 2025 15:04:31 GMT
content-type: text/html
content-length: 145
cf-ray: 971a8b3f6ce1eeb1-WAW
last-modified: Mon, 17 Aug 2020 20:44:06 GMT
x-amz-version-id: O7wYu3k8MISp4p_IZsFDHoAPVN3qn3tW
etag: "bffd99065e12d4ea9130af82fac8b3d0"
x-amz-error-code: NoSuchKey
x-amz-error-message: The specified key does not exist.
x-amz-error-detail-key: beta/binary/15.0.0/linux-x64/develop-f6e0744e38f6b86af49ea3b036bedbe45a672008/cypress.zip
x-amz-request-id: G3M298N0Z1G2WS3R
x-amz-id-2: z2iaFPACuJ7oRfNkrQtyXKf8HhkY709pAagowrYSBtB+6bC9JCdvl4rnIpX//3q3rfC227vxDxc=
age: 30017
cache-control: max-age=31536000
cf-cache-status: HIT
server: cloudflare

HTTP/2 200
date: Tue, 19 Aug 2025 15:04:32 GMT
content-type: application/zip
content-length: 211127906
cf-ray: 971a8b40a810b61a-WAW
x-amz-id-2: 6TbSwDUR5tu3H5gWjIdeYIwdHZG8C9kLqanycG331urBD+mdF6eZM9AZdwWH9xZ6+AIH9O4quTvdChbbnFT+Spi7/xEYbZwa
x-amz-request-id: CX8JYJY86K8WQMPM
x-amz-meta-checksum: 5f0d7e879e54e65a09c464fc7be6f8bf073f9ae236ff889b50e7621937c33b460014a04dbb303a266376b660e1e22e5a38e8981b4c834b12b3f5ebd0af1a9c3e
x-amz-meta-size: 211127906
last-modified: Mon, 18 Aug 2025 16:22:51 GMT
x-amz-expiration: expiry-date="Sat, 18 Oct 2025 00:00:00 GMT", rule-id="Purge old beta files"
x-amz-version-id: KxpJN.IxQq9M8QsuK0.AhUXwOzcyPLgj
etag: "e83f1513e3d6ab4114febcb121a613f9"
cache-control: max-age=31536000
cf-cache-status: MISS
server: cloudflare

[AtofStryker]

@MikeMcC399 I just purged the zip url from the Cloudflare cache. Are you able to try now?

[MikeMcC399]

@AtofStryker

Many thanks for the cache purge! I was able to load this into a Cypress Docker image and successfully test with it in a Cypress Docker repo clone. So I'd expect a Cypress 15 release also to pass the test-project tests when that event happens.

BTW: All of the newer beta linux-x64 zip files give 404. I don't actually need them, but I just wanted to mention it. If you think I should open a separate issue for this please let me know.

[AtofStryker]

@MikeMcC399 this is unfortunately a persistent problem. We've talked about it as a team and would like to automate the cache clearing at some point. I can't remember if there is an issue for it or not, but it is on our radar.

[cypress-bot]

Released in 15.0.0.

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