fix(deps): update dependency p-limit to v5
This PR contains the following updates:
| Package | Type | Update | Change |
|---|---|---|---|
| p-limit | dependencies | major | ^3.1.0 -> ^5.0.0 |
| p-limit | dependencies | major | ^3.0.2 -> ^5.0.0 |
Release Notes
sindresorhus/p-limit (p-limit)
v5.0.0
Breaking
- Require Node.js 18
23d61ba
As a reminder, this package continues to require ESM. For TypeScript users, this includes having "module": "node16", "moduleResolution": "node16" in your tsconfig.
Fixes
v4.0.0
Breaking
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ 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 these updates again.
- [ ] If you want to rebase/retry this PR, check this box
This PR has been generated by Renovate Bot.
Changed Packages
| Package Name | Package Path | Changeset Bump | Current Version |
|---|---|---|---|
| @backstage-community/plugin-azure-devops-backend | workspaces/azure-devops/plugins/azure-devops-backend | patch | v0.6.5 |
| @backstage-community/plugin-cicd-statistics-module-gitlab | workspaces/cicd-statistics/plugins/cicd-statistics-module-gitlab | patch | v0.1.31 |
| @backstage-community/plugin-fossa | workspaces/fossa/plugins/fossa | patch | v0.2.67 |
| @backstage-community/plugin-github-pull-requests-board | workspaces/github-pull-requests-board/plugins/github-pull-requests-board | patch | v0.2.2 |
| @backstage-community/plugin-vault-backend | workspaces/vault/plugins/vault-backend | patch | v0.4.11 |
As of v4 p-limit is ESM only: https://github.com/sindresorhus/p-limit/releases/tag/v4.0.0
@vinzscam @freben should we close this for now then?
Yes! It should be ignored like this https://github.com/backstage/backstage/blob/237d7e832541fb990bdee0bd5af1840c3b790e1b/.github/renovate.json5#L62
Renovate Ignore Notification
Because you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future 5.x releases. But if you manually upgrade to 5.x then Renovate will re-enable minor and patch updates automatically.
If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.