Skip to content

chore(deps): lock file maintenance#185

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

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

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate Bot commented Nov 30, 2025

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 2 times, most recently from a566f8f to 20afa69 Compare December 3, 2025 18:33
@renovate renovate Bot force-pushed the renovate/lock-file-maintenance branch from 20afa69 to 2a1ef93 Compare December 31, 2025 13:45
@renovate renovate Bot force-pushed the renovate/lock-file-maintenance branch from 2a1ef93 to 2e14548 Compare January 8, 2026 18:47
@renovate renovate Bot force-pushed the renovate/lock-file-maintenance branch 2 times, most recently from cae6fb9 to a6c0780 Compare January 23, 2026 16:30
@renovate renovate Bot force-pushed the renovate/lock-file-maintenance branch from a6c0780 to c86d692 Compare February 2, 2026 18:52
@renovate renovate Bot force-pushed the renovate/lock-file-maintenance branch 2 times, most recently from 5417b11 to ea286b8 Compare February 17, 2026 17:17
@renovate renovate Bot force-pushed the renovate/lock-file-maintenance branch from ea286b8 to fb84e00 Compare March 5, 2026 15:44
@renovate renovate Bot force-pushed the renovate/lock-file-maintenance branch 2 times, most recently from c945cf5 to e4394b0 Compare March 18, 2026 15:44
@renovate renovate Bot force-pushed the renovate/lock-file-maintenance branch from e4394b0 to 6079b8d Compare March 29, 2026 19:11
@renovate renovate Bot force-pushed the renovate/lock-file-maintenance branch from 6079b8d to ae7fa40 Compare March 29, 2026 19:47
@renovate renovate Bot force-pushed the renovate/lock-file-maintenance branch from ae7fa40 to 2fe69d7 Compare March 29, 2026 20:05
@renovate renovate Bot force-pushed the renovate/lock-file-maintenance branch 2 times, most recently from f75aead to dedc818 Compare April 1, 2026 17:57
@renovate renovate Bot force-pushed the renovate/lock-file-maintenance branch 2 times, most recently from 4683e77 to 0dd2874 Compare April 4, 2026 22:00
@renovate renovate Bot force-pushed the renovate/lock-file-maintenance branch from 0dd2874 to d1a94a0 Compare April 29, 2026 14:17
@renovate
Copy link
Copy Markdown
Contributor Author

renovate Bot commented May 12, 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: pnpm-lock.yaml
Progress: resolved 1, reused 0, downloaded 0, added 0
Progress: resolved 41, reused 0, downloaded 21, added 0
Progress: resolved 45, reused 0, downloaded 34, added 0
Progress: resolved 105, reused 0, downloaded 43, added 0
Progress: resolved 165, reused 0, downloaded 149, added 0
Progress: resolved 261, reused 0, downloaded 243, added 0
Progress: resolved 333, reused 0, downloaded 308, added 0
Progress: resolved 370, reused 0, downloaded 336, added 0
Progress: resolved 383, reused 0, downloaded 351, added 0
Progress: resolved 477, reused 0, downloaded 395, added 0
Progress: resolved 481, reused 0, downloaded 433, added 0
Progress: resolved 497, reused 0, downloaded 456, added 0
Progress: resolved 545, reused 0, downloaded 481, added 0
Progress: resolved 605, reused 0, downloaded 535, added 0
Progress: resolved 683, reused 0, downloaded 595, added 0
Progress: resolved 736, reused 0, downloaded 630, added 0
Progress: resolved 787, reused 0, downloaded 682, added 0
Progress: resolved 792, reused 0, downloaded 722, added 0
 ERR_PNPM_NO_MATURE_MATCHING_VERSION  Version 8.59.3 (released 18 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/nice-move/garou

The latest release of @typescript-eslint/utils is "8.59.3". Published at 5/11/2026 5:40:54 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.59.4-alpha.0 published at 5/11/2026 5:49:21 PM

If you need the full list of all 2951 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

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