Skip to content

Update dependency cypress to v15 - #1724

Merged
Lance Munslow (munslowl) merged 3 commits into
mainfrom
renovate-cypress-15.x
Aug 29, 2025
Merged

Update dependency cypress to v15#1724
Lance Munslow (munslowl) merged 3 commits into
mainfrom
renovate-cypress-15.x

Conversation

@renovate

@renovate renovate Bot commented Aug 20, 2025

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
cypress (source) ^14.5.4 -> ^15.0.0 age confidence

Release Notes

cypress-io/cypress (cypress)

v15.0.0

Compare Source

Changelog: https://docs.cypress.io/app/references/changelog#15.0.0


Configuration

📅 Schedule: Branch creation - "after 9am every weekday,before 5pm every weekday" in timezone Europe/London, Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate

renovate Bot commented Aug 20, 2025

Copy link
Copy Markdown
Contributor Author

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json
npm warn Unknown env config "store". This will stop working in the next major version of npm.
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: cypress-axe@1.6.0
npm error Found: cypress@15.0.0
npm error node_modules/cypress
npm error   dev cypress@"^15.0.0" from the root project
npm error   peer cypress@">3.0.0" from cypress-file-upload@5.0.8
npm error   node_modules/cypress-file-upload
npm error     dev cypress-file-upload@"^5.0.8" from the root project
npm error
npm error Could not resolve dependency:
npm error peer cypress@"^10 || ^11 || ^12 || ^13 || ^14" from cypress-axe@1.6.0
npm error node_modules/cypress-axe
npm error   dev cypress-axe@"^1.6.0" from the root project
npm error
npm error Conflicting peer dependency: cypress@14.5.4
npm error node_modules/cypress
npm error   peer cypress@"^10 || ^11 || ^12 || ^13 || ^14" from cypress-axe@1.6.0
npm error   node_modules/cypress-axe
npm error     dev cypress-axe@"^1.6.0" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /runner/cache/others/npm/_logs/2025-08-20T20_51_09_848Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2025-08-20T20_51_09_848Z-debug-0.log

@renovate

renovate Bot commented Aug 21, 2025

Copy link
Copy Markdown
Contributor Author

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

@munslowl

Copy link
Copy Markdown
Contributor

We will need to wait for the following PR to be approved, merged, and a new version of cypress-axe released:

component-driven/cypress-axe#187

@munslowl
Lance Munslow (munslowl) merged commit a6f82cf into main Aug 29, 2025
4 checks passed
@munslowl
Lance Munslow (munslowl) deleted the renovate-cypress-15.x branch August 29, 2025 09:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants