Skip to content

chore: lock file maintenance#11544

Open
renovate[bot] wants to merge 1 commit intomasterfrom
renovate/lock-file-maintenance
Open

chore: lock file maintenance#11544
renovate[bot] wants to merge 1 commit intomasterfrom
renovate/lock-file-maintenance

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate bot commented Apr 6, 2026

This PR contains the following updates:

Update Change
lockFileMaintenance All locks refreshed

🔧 This Pull Request updates lock files to use the latest dependency versions.


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • Between 12:00 AM and 03:59 AM, only on Monday (* 0-3 * * 1)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Enabled.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

Signed-off-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
@renovate renovate bot added the dependencies Pull requests that update a dependency file label Apr 6, 2026
@renovate
Copy link
Copy Markdown
Contributor Author

renovate bot commented Apr 6, 2026

⚠️ 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. See `npm help npmrc` for supported config options.
npm warn Unknown project config "scripts-prepend-node-path". This will stop working in the next major version of npm. See `npm help npmrc` for supported config options.
npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: @loopback/cli@7.0.12
npm error Found: mem-fs@4.1.4
npm error node_modules/mem-fs
npm error   dev mem-fs@"^4.1.4" from @loopback/cli@7.0.12
npm error   packages/cli
npm error     @loopback/cli@7.0.12
npm error     node_modules/@loopback/cli
npm error       workspace packages/cli from the root project
npm error
npm error Could not resolve dependency:
npm error peer mem-fs@"^2.1.0" from yeoman-test@6.3.0
npm error node_modules/yeoman-test
npm error   dev yeoman-test@"^6.3.0" from @loopback/cli@7.0.12
npm error   packages/cli
npm error     @loopback/cli@7.0.12
npm error     node_modules/@loopback/cli
npm error       workspace packages/cli from the root project
npm error
npm error Fix the upstream dependency conflict, or retry this command with --force or --legacy-peer-deps 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/2026-04-08T15_37_31_800Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-04-08T15_37_31_800Z-debug-0.log

@renovate renovate bot requested a review from raymondfeng as a code owner April 6, 2026 01:42
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.

0 participants