Skip to content

chore(deps): lock file maintenance#89

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

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

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Sep 20, 2021

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: Branch creation - "before 4am on monday" (UTC), 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
Copy link
Contributor Author

renovate bot commented Sep 20, 2021

Branch automerge failure

This PR was configured for branch automerge, however this is not possible so it has been raised as a PR instead.


  • Branch has one or more failed status checks

@renovate renovate bot force-pushed the renovate/lock-file-maintenance branch 5 times, most recently from 5e0dde3 to 6bbb571 Compare September 25, 2021 15:28
@renovate renovate bot force-pushed the renovate/lock-file-maintenance branch 6 times, most recently from 6c940af to 095474e Compare October 3, 2021 17:20
@renovate renovate bot force-pushed the renovate/lock-file-maintenance branch 5 times, most recently from 1a3ca9c to 02910de Compare October 12, 2021 22:24
@renovate renovate bot force-pushed the renovate/lock-file-maintenance branch 5 times, most recently from 039f3e2 to 1741b5a Compare October 21, 2021 05:21
@renovate renovate bot force-pushed the renovate/lock-file-maintenance branch 6 times, most recently from 9b621ec to bbbf698 Compare October 30, 2021 03:10
@renovate renovate bot force-pushed the renovate/lock-file-maintenance branch 2 times, most recently from 4b753da to 661751f Compare November 3, 2021 10:48
@renovate renovate bot force-pushed the renovate/lock-file-maintenance branch 5 times, most recently from 987ce5e to a054c9a Compare April 29, 2022 21:40
@renovate renovate bot force-pushed the renovate/lock-file-maintenance branch from a054c9a to fe06d94 Compare November 20, 2022 20:30
@renovate renovate bot force-pushed the renovate/lock-file-maintenance branch 16 times, most recently from f419bff to e3d0cf2 Compare March 24, 2023 15:13
@renovate renovate bot force-pushed the renovate/lock-file-maintenance branch 5 times, most recently from 7d10846 to 6ce7dfa Compare March 26, 2023 05:28
@renovate renovate bot force-pushed the renovate/lock-file-maintenance branch from 6ce7dfa to 2658e7a Compare March 28, 2023 03:36
@renovate
Copy link
Contributor Author

renovate bot commented Aug 10, 2025

⚠️ 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:2031) [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

Comments