Skip to content

chore(deps): lock file maintenance#149

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

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

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate Bot commented Apr 28, 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: (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: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, 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 608f10c to 6e7aba2 Compare August 13, 2025 12:38
@renovate renovate Bot force-pushed the renovate/lock-file-maintenance branch from 6e7aba2 to c78a526 Compare August 19, 2025 12:12
@renovate renovate Bot force-pushed the renovate/lock-file-maintenance branch from c78a526 to 249ef75 Compare August 31, 2025 11:59
@renovate renovate Bot force-pushed the renovate/lock-file-maintenance branch from 249ef75 to 058257b Compare September 25, 2025 17:57
@renovate renovate Bot force-pushed the renovate/lock-file-maintenance branch from 058257b to 4df616e Compare October 21, 2025 18:12
@renovate renovate Bot force-pushed the renovate/lock-file-maintenance branch from 4df616e to adf081c Compare November 10, 2025 22:43
@renovate renovate Bot force-pushed the renovate/lock-file-maintenance branch from adf081c to a35092d Compare November 18, 2025 23:40
@renovate renovate Bot force-pushed the renovate/lock-file-maintenance branch from a35092d to b61be6e Compare December 3, 2025 16:31
@renovate renovate Bot force-pushed the renovate/lock-file-maintenance branch from b61be6e to 3142a3f Compare December 31, 2025 18:49
@renovate renovate Bot force-pushed the renovate/lock-file-maintenance branch from 3142a3f to 5d2fd12 Compare January 8, 2026 21:24
@renovate renovate Bot force-pushed the renovate/lock-file-maintenance branch 2 times, most recently from 8ee777e to b0918c8 Compare January 23, 2026 20:59
@renovate renovate Bot force-pushed the renovate/lock-file-maintenance branch from b0918c8 to 52ebda2 Compare February 2, 2026 15:42
@renovate renovate Bot force-pushed the renovate/lock-file-maintenance branch 2 times, most recently from 7bcb947 to 4cc4d27 Compare February 17, 2026 18:10
@renovate renovate Bot force-pushed the renovate/lock-file-maintenance branch from 4cc4d27 to ef4c85d Compare March 5, 2026 17:11
@renovate renovate Bot force-pushed the renovate/lock-file-maintenance branch from ef4c85d to 866986a Compare March 13, 2026 13:19
@renovate renovate Bot force-pushed the renovate/lock-file-maintenance branch from 866986a to 5d3ba65 Compare April 1, 2026 21:46
@renovate
Copy link
Copy Markdown
Contributor Author

renovate Bot commented Apr 8, 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
(node:1697) [DEP0169] DeprecationWarning: `url.parse()` behavior is not standardized and prone to errors that have security implications. Use the WHATWG URL API instead. CVEs are not issued for `url.parse()` vulnerabilities.
(Use `node --trace-deprecation ...` to show where the warning was created)

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