chore(deps): update patch-package to snap-shot-core 10.2.4

[MikeMcC399]

• Closes patch-package warning for snap-shot-core #31440

Additional details

Issue background

• Dependabot PR chore(deps): update dependency snap-shot-it to v7.9.10 #31386, merged on Mar 27, 2025, bumped all usage of snap-shot-it to [email protected]
• [email protected] is a dependency of [email protected]
• Cypress currently contains patches/snap-shot-core+10.2.0.dev.patch
• When installing dependencies with yarn a warning "Warning: patch-package detected a patch file version mismatch" appears
• There are no code changes between the two versions according to bahmutov/snap-shot-core@v10.2.0...v10.2.4, only dependency differences.

Changes made

Renamed

• patches/snap-shot-core+10.2.0.dev.patch

to

• patches/snap-shot-core+10.2.4.dev.patch

Steps to test

git clone https://github.com/cypress-io/cypress
cd cypress
yarn

Confirm no warnings when patches are applied:

patch-package 6.4.7
Applying patches...
@types/[email protected] ✔
@urql/[email protected] ✔
[email protected] ✔
[email protected] ✔
[email protected] ✔
[email protected] ✔
[email protected] ✔
[email protected] ✔
[email protected] ✔
[email protected] ✔
[email protected] ✔

How has the user experience changed?

This change removes a warning for contributors. There should be no change for end-users of Cypress.

PR Tasks

• [na] Have tests been added/updated?
• [na] Has a PR for user-facing changes been opened in cypress-documentation?
• [na] Have API changes been updated in the type definitions?

[cypress-app-bot]

• Create a Draft Pull Request if your PR is not ready for review. Mark the PR as Ready for Review when you're ready for a Cypress team member to review the PR.

[MikeMcC399]

Patch is now successfully applied.

See https://app.circleci.com/pipelines/github/cypress-io/cypress/69225/workflows/76e467cf-448f-4a2a-8003-85131130a9e1/jobs/2846326?invite=true#step-118-27207_19

[jennifer-shehane]

@MikeMcC399 I'm wondering if we should parse the output in the npm install to look for ''Warning: patch-package detected a patch file version mismatch. We keep running into these issues with patch-package failures not being very obvious. Gonna discuss with the team. Or maybe fail on warnings...

[MikeMcC399]

@jennifer-shehane

I'm wondering if we should parse the output in the npm install to look for ''Warning: patch-package detected a patch file version mismatch. We keep running into these issues with patch-package failures not being very obvious. Gonna discuss with the team. Or maybe fail on warnings...

I only noticed this when I was running yarn locally.

CI should probably fail on "Warning: patch-package detected a patch file version mismatch" which would enable the problem to be identified and fixed together with the PR that triggered the version mismatch before it got merged.

[jennifer-shehane]

I think something is broken in contributor PRs here.

[jennifer-shehane]

Maybe something around this line

TESTFILES=$(find src -regextype posix-extended -name '*.cy.*' -not -regex '.*(FileMatch|PromoAction|SelectorPlayground|useDurationFormat|useTestingType|SpecPatterns).cy.*' | circleci tests split --total=$CIRCLE_NODE_TOTAL)

[MikeMcC399]

@jennifer-shehane

I think something is broken in contributor PRs here.

The changes in this PR should not affect anything apart from the warning from patch-package.

Would you like to submit this change yourself and close this PR or do you think you can solve the CI issue?

It would probably be good to get the patch warning fixed before the next release, but that would be your call.

[jennifer-shehane]

@MikeMcC399 Yah, I'll open a new PR. Someone is going to look into the contributor issue today.

[jennifer-shehane]

Opened here: #31449

[jennifer-shehane]

Issue for contributor PR problem: #31450