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

fix(deps): update dependency eslint-plugin-lodash to v8 #123

Closed
wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jul 2, 2024

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
eslint-plugin-lodash ^7.4.0 -> ^8.0.0 age adoption passing confidence

Release Notes

idok/eslint-plugin-lodash (eslint-plugin-lodash)

v8.0.0

Compare Source


Configuration

📅 Schedule: Branch creation - "after 4:00 am on Friday on the 1st through 7th day of the month every 3 month" in timezone Australia/Melbourne, 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.

@renovate renovate bot added the dependencies Pull requests that update a dependency file label Jul 2, 2024
@renovate renovate bot requested a review from bchew July 2, 2024 00:04
Copy link
Contributor Author

renovate bot commented Jul 2, 2024

⚠️ 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 error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: [email protected]
npm error Found: [email protected]
npm error node_modules/eslint
npm error   peer eslint@"^8.57.0" from the root project
npm error
npm error Could not resolve dependency:
npm error peer eslint@">=9.0.0" from [email protected]
npm error node_modules/eslint-plugin-lodash
npm error   eslint-plugin-lodash@"^8.0.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 /tmp/renovate/cache/others/npm/_logs/2024-07-02T00_04_15_339Z-eresolve-report.txt

npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-07-02T00_04_15_339Z-debug-0.log

@renovate renovate bot requested a review from xiaofan2406 July 2, 2024 00:04
@bchew bchew closed this Jul 2, 2024
@bchew bchew reopened this Jul 2, 2024
@bchew bchew closed this Jul 2, 2024
@bchew bchew deleted the renovate-major-lodash branch July 2, 2024 00:12
Copy link

sonarcloud bot commented Jul 2, 2024

Copy link
Contributor Author

renovate bot commented Jul 2, 2024

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future 8.x releases. But if you manually upgrade to 8.x then Renovate will re-enable minor and patch updates automatically.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant