Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(deps): update dependency sinon to v13.0.2 (master) #1235

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Apr 14, 2022

This PR contains the following updates:

Package Type Update Change OpenSSF
sinon (source) devDependencies patch 13.0.1 -> 13.0.2 OpenSSF Scorecard

Release Notes

sinonjs/sinon (sinon)

v13.0.2

Compare Source

  • bddb631a
    Update fake-timers (Carl-Erik Kopseng)
  • eaed0eb2
    Bump nokogiri from 1.13.3 to 1.13.4 (#​2451) (dependabot[bot])

Released by Carl-Erik Kopseng on 2022-04-14.


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

Rebasing: Whenever PR is behind base branch, 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
Copy link
Contributor Author

renovate bot commented Apr 14, 2022

⚠ 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 cli npm v10.2.3 does not support Node.js v16.20.2. This version of npm supports the following node versions: `^18.17.0 || >=20.5.0`. You can find the latest version at https://nodejs.org/.
npm WARN cli npm v10.2.3 does not support Node.js v16.20.2. This version of npm supports the following node versions: `^18.17.0 || >=20.5.0`. You can find the latest version at https://nodejs.org/.
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: [email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/react
npm ERR!   dev react@"17.0.2" from the root project
npm ERR!   peer react@"17.0.2" from [email protected]
npm ERR!   node_modules/react-dom
npm ERR!     dev react-dom@"17.0.2" from the root project
npm ERR!   1 more (react-redux)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer react@"^15.4.0 || ^16.0.0" from [email protected]
npm ERR! node_modules/material-ui
npm ERR!   dev material-ui@"0.20.2" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: [email protected]
npm ERR! node_modules/react
npm ERR!   peer react@"^15.4.0 || ^16.0.0" from [email protected]
npm ERR!   node_modules/material-ui
npm ERR!     dev material-ui@"0.20.2" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! 
npm ERR! For a full report see:
npm ERR! /tmp/worker/370555/9064d1/cache/others/npm/_logs/2023-11-13T15_51_19_365Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in: /tmp/worker/370555/9064d1/cache/others/npm/_logs/2023-11-13T15_51_19_365Z-debug-0.log

@renovate renovate bot force-pushed the renovate/master-sinon-13.x branch from a38c032 to e5ac771 Compare August 1, 2023 14:15
@renovate renovate bot force-pushed the renovate/master-sinon-13.x branch from e5ac771 to d263aee Compare November 13, 2023 15:51
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.

0 participants