Skip to content

chore(deps): lock file maintenance#191

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

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

Conversation

@renovate

@renovate renovate Bot commented Nov 30, 2025

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: (in timezone Asia/Shanghai)

  • 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 4f089ee to a859cd1 Compare December 3, 2025 19:29
@renovate
renovate Bot force-pushed the renovate/lock-file-maintenance branch from a859cd1 to 6edd928 Compare December 31, 2025 16:16
@renovate
renovate Bot force-pushed the renovate/lock-file-maintenance branch from 6edd928 to 12df78c Compare January 8, 2026 19:27
@renovate
renovate Bot force-pushed the renovate/lock-file-maintenance branch 3 times, most recently from a3f0dac to cd074a8 Compare January 23, 2026 18:15
@renovate
renovate Bot force-pushed the renovate/lock-file-maintenance branch from cd074a8 to b14421e Compare January 27, 2026 19:00
@renovate
renovate Bot force-pushed the renovate/lock-file-maintenance branch from b14421e to 2e2d3fa Compare February 3, 2026 10:40
@renovate
renovate Bot force-pushed the renovate/lock-file-maintenance branch 2 times, most recently from feb0ab3 to 82863fd Compare February 17, 2026 15:12
@renovate
renovate Bot force-pushed the renovate/lock-file-maintenance branch from 82863fd to 5df4464 Compare March 5, 2026 20:41
@renovate
renovate Bot force-pushed the renovate/lock-file-maintenance branch from 5df4464 to 53ae699 Compare March 13, 2026 17:06
@renovate
renovate Bot force-pushed the renovate/lock-file-maintenance branch 3 times, most recently from f4ddd14 to 6c5c846 Compare April 1, 2026 18:06
@renovate
renovate Bot force-pushed the renovate/lock-file-maintenance branch from 6c5c846 to 6f79b2b Compare April 4, 2026 22:50
@renovate
renovate Bot force-pushed the renovate/lock-file-maintenance branch from 6f79b2b to 1b4f3ce Compare April 29, 2026 09:49
@renovate
renovate Bot force-pushed the renovate/lock-file-maintenance branch from 1b4f3ce to df70dcf Compare May 18, 2026 10:43
@renovate
renovate Bot force-pushed the renovate/lock-file-maintenance branch from df70dcf to 6e9efd5 Compare May 28, 2026 18:33
@renovate
renovate Bot force-pushed the renovate/lock-file-maintenance branch from 6e9efd5 to d5b78e8 Compare June 11, 2026 15:41
@renovate
renovate Bot force-pushed the renovate/lock-file-maintenance branch from d5b78e8 to 06f95d6 Compare June 24, 2026 14:07
@renovate
renovate Bot force-pushed the renovate/lock-file-maintenance branch from 06f95d6 to 1c18207 Compare July 16, 2026 21:44
@renovate

renovate Bot commented Jul 20, 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: pnpm-lock.yaml
Progress: resolved 1, reused 0, downloaded 0, added 0
Progress: resolved 14, reused 0, downloaded 7, added 0
Progress: resolved 57, reused 0, downloaded 9, added 0
Progress: resolved 104, reused 0, downloaded 14, added 0
Progress: resolved 131, reused 0, downloaded 119, added 0
Progress: resolved 203, reused 0, downloaded 183, added 0
Progress: resolved 278, reused 0, downloaded 259, added 0
Progress: resolved 342, reused 0, downloaded 318, added 0
Progress: resolved 389, reused 0, downloaded 352, added 0
Progress: resolved 412, reused 0, downloaded 383, added 0
Progress: resolved 456, reused 0, downloaded 425, added 0
Progress: resolved 500, reused 0, downloaded 464, added 0
Progress: resolved 539, reused 0, downloaded 480, added 0
Progress: resolved 561, reused 0, downloaded 527, added 0
Progress: resolved 565, reused 0, downloaded 540, added 0
Progress: resolved 582, reused 0, downloaded 552, added 0
 ERR_PNPM_NO_MATURE_MATCHING_VERSION  Version 8.65.0 (released 5 hours ago) of @typescript-eslint/utils does not meet the minimumReleaseAge constraint

This error happened while installing a direct dependency of /tmp/renovate/repos/github/best-shot/babel-preset-evergreen

The latest release of @typescript-eslint/utils is "8.65.0". Published at 7/20/2026 5:39:03 PM

Other releases are:
  * rc-v: 6.0.0-alpha.58 published at 2/21/2023
  * rc-v6: 7.0.0-alpha.0 published at 7/10/2023
  * rc-v8: 8.0.0-alpha.62 published at 7/31/2024
  * canary: 8.65.1-alpha.1 published at 7/20/2026 7:28:44 PM

If you need the full list of all 3069 published versions run "pnpm view @typescript-eslint/utils versions".

If you want to install the matched version ignoring the time it was published, you can add the package name to the minimumReleaseAgeExclude setting. Read more about it: https://pnpm.io/settings#minimumreleaseageexclude
Progress: resolved 665, reused 0, downloaded 638, added 0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Development

Successfully merging this pull request may close these issues.

0 participants