Skip to content

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Jul 13, 2024

This PR contains the following updates:

Package Change Age Confidence
rimraf 6.0.0 -> 6.1.0 age confidence

Release Notes

isaacs/rimraf (rimraf)

v6.1.0

Compare Source

v6.0.1

Compare Source

v6.0.0

Compare Source

v5.0.10

Compare Source

v5.0.9

Compare Source

v5.0.8

Compare Source

v5.0.7

Compare Source

v5.0.6

Compare Source

v5.0.5

Compare Source

v5.0.4

Compare Source

v5.0.3

Compare Source

v5.0.2

Compare Source


Configuration

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

🚦 Automerge: Disabled because a matching PR was automerged previously.

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 added the dependencies Updates to dependencies label Jul 13, 2024
@renovate renovate bot requested a review from sgarner July 13, 2024 20:01
@renovate
Copy link
Contributor Author

renovate bot commented Jul 13, 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 warn Unknown env config "store". This will stop working in the next major version of npm.
npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: vue-apollo-smart-ops@0.2.0-beta.1
npm error Found: eslint@9.32.0
npm error node_modules/eslint
npm error   dev eslint@"9.32.0" from the root project
npm error
npm error Could not resolve dependency:
npm error peer eslint@"^2 || ^3 || ^4 || ^5 || ^6 || ^7.2.0 || ^8" from eslint-plugin-import@2.29.1
npm error node_modules/eslint-plugin-import
npm error   dev eslint-plugin-import@"2.29.1" 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-11-10T18_04_58_171Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2025-11-10T18_04_58_171Z-debug-0.log

@renovate renovate bot force-pushed the renovate/rimraf-6.x branch from c9650f6 to 6fe846d Compare July 16, 2024 20:18
@renovate renovate bot force-pushed the renovate/rimraf-6.x branch from 6fe846d to 4f03212 Compare January 17, 2025 04:19
@renovate renovate bot force-pushed the renovate/rimraf-6.x branch 2 times, most recently from 942eda2 to cbdb730 Compare February 16, 2025 21:52
@renovate renovate bot force-pushed the renovate/rimraf-6.x branch from cbdb730 to f2e024d Compare February 25, 2025 13:12
@renovate renovate bot force-pushed the renovate/rimraf-6.x branch from f2e024d to bd09949 Compare March 6, 2025 06:31
@renovate renovate bot force-pushed the renovate/rimraf-6.x branch 3 times, most recently from c5fb972 to 4f2688d Compare June 30, 2025 13:02
@renovate renovate bot force-pushed the renovate/rimraf-6.x branch from 4f2688d to b359ac1 Compare August 10, 2025 15:01
@renovate renovate bot force-pushed the renovate/rimraf-6.x branch from b359ac1 to 4efb08e Compare November 3, 2025 01:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Updates to dependencies

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant