fix(deps): update dependency mysql2 to v3.18.2 #5
Loading…
x
Reference in New Issue
Block a user
No description provided.
Delete Branch "renovate/mysql2-3.x-lockfile"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This PR contains the following updates:
3.14.0->3.18.2Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Renovate Bot.
⚠️ 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:
The artifact failure details are included below:
File name: pnpm-lock.yaml
948858764dtof9b0dd0a27f9b0dd0a27to5c1795b3d8fix(deps): update dependency mysql2 to v3.14.1to fix(deps): update dependency mysql2 to v3.14.25c1795b3d8to51227759f1fix(deps): update dependency mysql2 to v3.14.2to fix(deps): update dependency mysql2 to v3.14.351227759f1toaca301e224fix(deps): update dependency mysql2 to v3.14.3to fix(deps): update dependency mysql2 to v3.14.4fix(deps): update dependency mysql2 to v3.14.4to fix(deps): update dependency mysql2 to v3.14.5aca301e224toc43e126868c43e126868toa9eac5eed7fix(deps): update dependency mysql2 to v3.14.5to fix(deps): update dependency mysql2 to v3.15.0fix(deps): update dependency mysql2 to v3.15.0to fix(deps): update dependency mysql2 to v3.15.1a9eac5eed7toe0ea52b9a1fix(deps): update dependency mysql2 to v3.15.1to fix(deps): update dependency mysql2 to v3.15.2e0ea52b9a1to85cbf0769bfix(deps): update dependency mysql2 to v3.15.2to fix(deps): update dependency mysql2 to v3.15.385cbf0769bto3770328dfc3770328dfctoad62fe5ec5fix(deps): update dependency mysql2 to v3.15.3to fix(deps): update dependency mysql2 to v3.16.0ad62fe5ec5tod6769ea17fd6769ea17ftoc1b9ff7724fix(deps): update dependency mysql2 to v3.16.0to fix(deps): update dependency mysql2 to v3.16.1c1b9ff7724tod19480c41afix(deps): update dependency mysql2 to v3.16.1to fix(deps): update dependency mysql2 to v3.16.2d19480c41ato14ab06236014ab062360to36b1f59786fix(deps): update dependency mysql2 to v3.16.2to fix(deps): update dependency mysql2 to v3.16.336b1f59786to7d0b6ac3ddfix(deps): update dependency mysql2 to v3.16.3to fix(deps): update dependency mysql2 to v3.17.07d0b6ac3ddto0bf64f14de0bf64f14detob7cd744851b7cd744851to773ad604f6fix(deps): update dependency mysql2 to v3.17.0to fix(deps): update dependency mysql2 to v3.17.1fix(deps): update dependency mysql2 to v3.17.1to fix(deps): update dependency mysql2 to v3.17.2773ad604f6to017e024e49fix(deps): update dependency mysql2 to v3.17.2to fix(deps): update dependency mysql2 to v3.17.3017e024e49to0239adc8a7fix(deps): update dependency mysql2 to v3.17.3to fix(deps): update dependency mysql2 to v3.17.40239adc8a7to0f712358cf0f712358cfto933a5105e7fix(deps): update dependency mysql2 to v3.17.4to fix(deps): update dependency mysql2 to v3.17.5fix(deps): update dependency mysql2 to v3.17.5to fix(deps): update dependency mysql2 to v3.18.0933a5105e7toc05daeb39afix(deps): update dependency mysql2 to v3.18.0to fix(deps): update dependency mysql2 to v3.18.1c05daeb39atoe120d7d788e120d7d788to7e7d1e80d9fix(deps): update dependency mysql2 to v3.18.1to fix(deps): update dependency mysql2 to v3.18.27e7d1e80d9to381a6dc1b7381a6dc1b7toa535619638Checkout
From your project repository, check out a new branch and test the changes.