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 stylelint to v16 #97

Merged
merged 1 commit into from
Dec 8, 2023

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Dec 8, 2023

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
stylelint (source) ^15.1.0 -> ^16.0.0 age adoption passing confidence

Release Notes

stylelint/stylelint (stylelint)

v16.0.0

Compare Source

Migrating to 16.0.0 guide.


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), 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 has been generated by Mend Renovate. View repository job log here.

Copy link
Contributor Author

renovate bot commented Dec 8, 2023

⚠ 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 ERESOLVE overriding peer dependency
npm WARN While resolving: [email protected]
npm WARN Found: [email protected]
npm WARN node_modules/stylelint
npm WARN   dev stylelint@"^16.0.0" from the root project
npm WARN 
npm WARN Could not resolve dependency:
npm WARN peer stylelint@"^15.10.0" from [email protected]
npm WARN node_modules/stylelint-config-recommended
npm WARN   stylelint-config-recommended@"^13.0.0" from [email protected]
npm WARN   node_modules/stylelint-config-recommended-scss
npm WARN   1 more (stylelint-config-standard)
npm WARN 
npm WARN Conflicting peer dependency: [email protected]
npm WARN node_modules/stylelint
npm WARN   peer stylelint@"^15.10.0" from [email protected]
npm WARN   node_modules/stylelint-config-recommended
npm WARN     stylelint-config-recommended@"^13.0.0" from [email protected]
npm WARN     node_modules/stylelint-config-recommended-scss
npm WARN     1 more (stylelint-config-standard)
npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving: [email protected]
npm WARN Found: [email protected]
npm WARN node_modules/stylelint
npm WARN   dev stylelint@"^16.0.0" from the root project
npm WARN 
npm WARN Could not resolve dependency:
npm WARN peer stylelint@"^15.10.0" from [email protected]
npm WARN node_modules/stylelint-config-recommended-scss
npm WARN   stylelint-config-recommended-scss@"^13.1.0" from [email protected]
npm WARN   node_modules/stylelint-config-standard-scss
npm WARN 
npm WARN Conflicting peer dependency: [email protected]
npm WARN node_modules/stylelint
npm WARN   peer stylelint@"^15.10.0" from [email protected]
npm WARN   node_modules/stylelint-config-recommended-scss
npm WARN     stylelint-config-recommended-scss@"^13.1.0" from [email protected]
npm WARN     node_modules/stylelint-config-standard-scss
npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving: [email protected]
npm WARN Found: [email protected]
npm WARN node_modules/stylelint
npm WARN   dev stylelint@"^16.0.0" from the root project
npm WARN 
npm WARN Could not resolve dependency:
npm WARN peer stylelint@"^15.10.0" from [email protected]
npm WARN node_modules/stylelint-config-standard
npm WARN   stylelint-config-standard@"^34.0.0" from [email protected]
npm WARN   node_modules/stylelint-config-standard-scss
npm WARN 
npm WARN Conflicting peer dependency: [email protected]
npm WARN node_modules/stylelint
npm WARN   peer stylelint@"^15.10.0" from [email protected]
npm WARN   node_modules/stylelint-config-standard
npm WARN     stylelint-config-standard@"^34.0.0" from [email protected]
npm WARN     node_modules/stylelint-config-standard-scss
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/stylelint
npm ERR!   dev stylelint@"^16.0.0" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer stylelint@"^15.10.0" from [email protected]
npm ERR! node_modules/stylelint-config-standard-scss
npm ERR!   dev stylelint-config-standard-scss@"^11.0.0" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: [email protected]
npm ERR! node_modules/stylelint
npm ERR!   peer stylelint@"^15.10.0" from [email protected]
npm ERR!   node_modules/stylelint-config-standard-scss
npm ERR!     dev stylelint-config-standard-scss@"^11.0.0" 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/renovate/cache/others/npm/_logs/2023-12-08T14_10_41_559Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2023-12-08T14_10_41_559Z-debug-0.log

@mergify mergify bot merged commit be5b650 into main Dec 8, 2023
1 of 3 checks passed
@renovate renovate bot deleted the renovate/stylelint-16.x branch December 8, 2023 14:11
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