Skip to content

chore(deps): lock file maintenance#62

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

chore(deps): lock file maintenance#62
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/lock-file-maintenance

Conversation

@renovate

@renovate renovate Bot commented Apr 13, 2026

Copy link
Copy Markdown
Contributor

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.

@renovate
renovate Bot force-pushed the renovate/lock-file-maintenance branch from 746e71d to 88be901 Compare April 29, 2026 10:14
@renovate
renovate Bot force-pushed the renovate/lock-file-maintenance branch 4 times, most recently from 1e560a2 to 97316b2 Compare May 18, 2026 12:16
@renovate
renovate Bot force-pushed the renovate/lock-file-maintenance branch 2 times, most recently from ad094e0 to 9505cf9 Compare June 1, 2026 19:05
@renovate
renovate Bot force-pushed the renovate/lock-file-maintenance branch from 9505cf9 to abfd879 Compare June 11, 2026 19:35
@renovate

renovate Bot commented Jul 12, 2026

Copy link
Copy Markdown
Contributor Author

⚠️ 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 error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: wrangler@4.111.0
npm error Found: @cloudflare/workers-types@4.20260702.1
npm error node_modules/@cloudflare/workers-types
npm error   dev @cloudflare/workers-types@"^4.20260511.1" from the root project
npm error
npm error Could not resolve dependency:
npm error peerOptional @cloudflare/workers-types@"^5.20260710.1" from wrangler@4.111.0
npm error node_modules/wrangler
npm error   dev wrangler@"^4.90.0" from the root project
npm error
npm error Conflicting peer dependency: @cloudflare/workers-types@5.20260716.1
npm error node_modules/@cloudflare/workers-types
npm error   peerOptional @cloudflare/workers-types@"^5.20260710.1" from wrangler@4.111.0
npm error   node_modules/wrangler
npm error     dev wrangler@"^4.90.0" 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-07-16T17_57_11_411Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-07-16T17_57_11_411Z-debug-0.log

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