svelte-fullcalendar
svelte-fullcalendar copied to clipboard
chore(deps): update dependency cypress to v10
This PR contains the following updates:
| Package | Change | Age | Adoption | Passing | Confidence |
|---|---|---|---|---|---|
| cypress | 9.7.0 -> 10.8.0 |
Release Notes
cypress-io/cypress
v10.8.0
Changelog: https://docs.cypress.io/guides/references/changelog#10-8-0
v10.7.0
Changelog: https://docs.cypress.io/guides/references/changelog#​10-7-0
v10.6.0
Changelog: https://docs.cypress.io/guides/references/changelog#10-6-0
v10.5.0
Changelog: https://docs.cypress.io/guides/references/changelog#10-5-0
v10.4.0
Changelog: https://docs.cypress.io/guides/references/changelog#10-4-0
v10.3.1
Changelog: https://docs.cypress.io/guides/references/changelog#10-3-1
v10.3.0
Changelog: https://docs.cypress.io/guides/references/changelog#10-3-0
v10.2.0
Changelog: https://docs.cypress.io/guides/references/changelog#10-2-0
v10.1.0
Changelog: https://docs.cypress.io/guides/references/changelog#10-1-0
v10.0.3
Changelog: https://docs.cypress.io/guides/references/changelog#10-0-3
v10.0.2
Changelog: https://docs.cypress.io/guides/references/changelog#10-0-2
v10.0.1
Changelog: https://docs.cypress.io/guides/references/changelog#10-0-1
v10.0.0
Changelog: https://docs.cypress.io/guides/references/changelog#10-0-0
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled due to failing status checks.
♻ 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, click this checkbox.
This PR has been generated by Mend Renovate. View repository job log here.
⚠ 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: pnpm-lock.yaml
installing v2 tool node v16.17.1
linking tool node v16.17.1
node: v16.17.1 /usr/local/bin/node
npm: 8.15.0 /usr/local/bin/npm
Installed v2 /usr/local/buildpack/tools/v2/node.sh in 6 seconds
skip cleanup, not a docker build: 0c22f9ad198d
installing v2 tool pnpm v7.12.2
added 1 package in 3s
linking tool pnpm v7.12.2
7.12.2
Installed v2 /usr/local/buildpack/tools/v2/pnpm.sh in 5 seconds
skip cleanup, not a docker build: 0c22f9ad198d
Scope: all 3 workspace projects
Progress: resolved 1, reused 0, downloaded 0, added 0
Progress: resolved 10, reused 0, downloaded 3, added 0
Progress: resolved 15, reused 0, downloaded 11, added 0
Progress: resolved 16, reused 0, downloaded 14, added 0
Progress: resolved 18, reused 0, downloaded 16, added 0
Progress: resolved 21, reused 0, downloaded 18, added 0
Progress: resolved 22, reused 0, downloaded 18, added 0
Progress: resolved 23, reused 0, downloaded 19, added 0
Progress: resolved 23, reused 0, downloaded 20, added 0
Progress: resolved 23, reused 0, downloaded 21, added 0
Progress: resolved 23, reused 0, downloaded 23, added 0
Progress: resolved 24, reused 0, downloaded 23, added 0
Progress: resolved 25, reused 0, downloaded 23, added 0
Progress: resolved 46, reused 0, downloaded 26, added 0
Progress: resolved 68, reused 0, downloaded 46, added 0
Progress: resolved 92, reused 0, downloaded 70, added 0
Progress: resolved 114, reused 0, downloaded 96, added 0
Progress: resolved 131, reused 0, downloaded 117, added 0
Progress: resolved 156, reused 0, downloaded 139, added 0
Progress: resolved 178, reused 0, downloaded 159, added 0
Progress: resolved 191, reused 0, downloaded 166, added 0
Progress: resolved 206, reused 0, downloaded 183, added 0
Progress: resolved 226, reused 0, downloaded 198, added 0
Progress: resolved 249, reused 0, downloaded 215, added 0
Progress: resolved 271, reused 0, downloaded 238, added 0
Progress: resolved 291, reused 0, downloaded 253, added 0
Progress: resolved 317, reused 0, downloaded 273, added 0
Progress: resolved 339, reused 0, downloaded 282, added 0
Progress: resolved 366, reused 0, downloaded 303, added 0
Progress: resolved 386, reused 0, downloaded 319, added 0
Progress: resolved 396, reused 0, downloaded 347, added 0
Progress: resolved 434, reused 0, downloaded 369, added 0
Progress: resolved 443, reused 0, downloaded 385, added 0
Progress: resolved 454, reused 0, downloaded 397, added 0
Progress: resolved 478, reused 0, downloaded 423, added 0
Progress: resolved 492, reused 0, downloaded 436, added 0
Progress: resolved 520, reused 0, downloaded 467, added 0
Progress: resolved 520, reused 0, downloaded 476, added 0
Progress: resolved 521, reused 0, downloaded 477, added 0
Progress: resolved 521, reused 0, downloaded 479, added 0, done
ERR_PNPM_PEER_DEP_ISSUES Unmet peer dependencies
examples/kit
└─┬ @sveltejs/kit 1.0.0-next.504
└── ✕ unmet peer vite@^3.1.0: found 3.0.2
hint: If you don't want pnpm to fail on peer dependency issues, add "strict-peer-dependencies=false" to an .npmrc file at the root of your project.