Bump js-yaml and @cypress/code-coverage in /packages/end-to-end

[dependabot]

Bumps js-yaml to 4.2.0 and updates ancestor dependency @cypress/code-coverage. These dependencies need to be updated together.

Updates js-yaml from 4.1.0 to 4.2.0

Changelog

Sourced from js-yaml's changelog.

[4.2.0] - 2026-06-01

Added

• Added docs/safety.md with notes about processing untrusted YAML.
• Added maxDepth (100) loader option. Not a problem, but gives a better exception instead of RangeError on stack overflow.
• Added maxMergeSeqLength (20) loader option. Not a problem after merge fix, but an additional restriction for safety.
• Added sourcemaps to dist/ builds.

Changed

• Stop resolving numbers with underscores as numeric scalars, #627.
• Switched dev toolchains to Vite / neostandard.
• Updated demo.
• Reorganized tests.
• dist/ files are no longer kept in the repository.

Fixed

• Fix parsing of properties on the first implicit block mapping key, #62.
• Fix trailing whitespace handling when folding flow scalar lines, #307.
• Reject top-level block scalars without content indentation, #280.
• Ensure numbers survive round-trip, #737.
• Fix test coverage for issue #221.
• Fix flow scalar trailing whitespace folding, #307.
• Fix digits in YAML named tag handles.

Security

• Fix potential DoS via quadratic complexity in merge - deduplicate repeated elements (makes sense for malformed files > 10K).

[3.14.2] - 2025-11-15

Security

• Backported v4.1.1 fix to v3

[4.1.1] - 2025-11-12

Security

• Fix prototype pollution issue in yaml merge (<<) operator.

Commits

• See full diff in compare view

Updates @cypress/code-coverage from 3.12.1 to 4.0.3

Release notes

Sourced from @​cypress/code-coverage's releases.

v4.0.3

4.0.3 (2026-03-23)

Bug Fixes

• deps: update dependency debug to v4.4.3 (#990) (985dbdd)

v4.0.2

4.0.2 (2026-03-16)

Bug Fixes

• deps: update dependency dayjs to v1.11.20 (#988) (0540776)

v4.0.1

4.0.1 (2026-02-26)

Bug Fixes

• deps: update dependency dayjs to v1.11.19 (#983) (a9a10f4)

v4.0.0

4.0.0 (2026-02-10)

chore

• release next major version (#979) (29455d8)

BREAKING CHANGES

• Configure with expose rather than env. Minimum Cypress version is now v15.10.0. Minimum node version is now 20.x.

v3.14.7

3.14.7 (2025-10-08)

Bug Fixes

• deps: switch to tinyglobby (#960) (41d9b3d)

v3.14.6

3.14.6 (2025-08-19)

Bug Fixes

... (truncated)

Commits

• 995b23a chore(deps): update dependency @​types/debug to v4.1.13 (#989)
• 985dbdd fix(deps): update dependency debug to v4.4.3 (#990)
• 72e4299 chore(deps): update dependency serve to v14.2.6 (#987)
• 0540776 fix(deps): update dependency dayjs to v1.11.20 (#988)
• fbe9918 chore(deps): update dependency @​types/lodash to v4.17.24 (#984)
• 649cf9d chore(deps): update nyc, babel-plugin-istanbul, rimraf, and semantic-release ...
• a9a10f4 fix(deps): update dependency dayjs to v1.11.19 (#983)
• 067c87c chore(deps): update dependency win to v5.1.1 (#982)
• 67df880 chore(deps): update dependency lodash to v4.17.23 (#980)
• fd56f59 chore(deps): update dependency serve to v14.2.5 (#981)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  You can disable automated security fix PRs for this repo from the Security Alerts page.

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	@​cypress/​code-coverage@​3.12.1 ⏵ 4.0.3

View full report

[socket-security]

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert  (click "▶" to expand/collapse)
Warn		Obfuscated code: npm js-yaml is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: packages/end-to-end/package-lock.json → npm/@cypress/code-coverage@4.0.3 → npm/eslint@8.43.0 → npm/js-yaml@4.2.0 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/js-yaml@4.2.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Obfuscated code: npm webpack is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: packages/end-to-end/package-lock.json → npm/@cypress/code-coverage@4.0.3 → npm/webpack@5.107.2 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/webpack@5.107.2. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report