Update dependency p-limit to v7

[gardener-ci-robot]

This PR contains the following updates:

Package	Change	Age	Confidence
p-limit	3.1.0 → 7.3.0

---

Release Notes

sindresorhus/p-limit (p-limit)

v7.3.0

Compare Source

• Add rejectOnClear option 8907801
• Support options object in pLimit() 870db0f

---

v7.2.0

Compare Source

• Make .map() method accept an iterable, not just array (#​98) d76231b

---

v7.1.1

Compare Source

• Fix limitFunction type ccb80b2

---

v7.1.0

Compare Source

• Add index parameter to map() method 2aeffd4

---

v7.0.0

Compare Source

Breaking

• Require Node.js 20 78b81a5
• activeCount now increments when tasks actually start running (more intuitive) rather than when queued. This means:
  • activeCount reflects truly active/running promises
  • pendingCount more accurately represents waiting

Improvements

• Add .map convenience method 86a5d73
• Improve performance (#​93) be1965b

---

v6.2.0

Compare Source

• Add limitFunction() (#​88) ef48184

v6.1.0

Compare Source

• Allow changing concurrency limit (#​79) 3e4fdd1

v6.0.0

Compare Source

• Improve performance (#​83) 80273d7
  • This is a major version because it slightly changes the timing of .activeCount and .pendingCount. This is unlikely to affect most users, but I wanted to play it safe. Learn more.

v5.0.0

Compare Source

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

• Fix AsyncResource propagation issue (#​71) ad8afe6

v4.0.0

Compare Source

Breaking

• Require Node.js 12.20 9e08401
• This package is now pure ESM. Please read this.

---

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 becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Renovate Bot.

[gardener-robot]

@grolu, @holgerkoser, @klocke-io You have pull request review open invite, please check

[gardener-ci-robot]

The Gardener project currently lacks enough active contributors to adequately respond to all PRs.
This bot triages PRs according to the following rules:

• After 15d of inactivity, lifecycle/stale is applied
• After 15d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 7d of inactivity since lifecycle/rotten was applied, the PR is closed

You can:

• Mark this PR as fresh with /remove-lifecycle stale
• Mark this PR as rotten with /lifecycle rotten
• Close this PR with /close

/lifecycle stale

[gardener-prow]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign petersutter for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[gardener-ci-robot]

The Gardener project currently lacks enough active contributors to adequately respond to all PRs.
This bot triages PRs according to the following rules:

• After 30d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 14d of inactivity since lifecycle/rotten was applied, the PR is closed

You can:

• Mark this PR as active with /lifecycle active
• Mark this PR as fresh with /remove-lifecycle rotten
• Close this PR with /close

/lifecycle rotten

[gardener-ci-robot]

The Gardener project currently lacks enough active contributors to adequately respond to all PRs.
This bot triages PRs according to the following rules:

• After 30d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 14d of inactivity since lifecycle/rotten was applied, the PR is closed

You can:

• Reopen this PR with /reopen
• Mark this PR as active with /lifecycle active
• Mark this PR as fresh with /remove-lifecycle rotten

/close

[gardener-prow]

@gardener-ci-robot: Closed this PR.

Details

In response to this:

The Gardener project currently lacks enough active contributors to adequately respond to all PRs.
This bot triages PRs according to the following rules:

• After 30d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 14d of inactivity since lifecycle/rotten was applied, the PR is closed

You can:

• Reopen this PR with /reopen
• Mark this PR as active with /lifecycle active
• Mark this PR as fresh with /remove-lifecycle rotten

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[gardener-ci-robot]

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future 7.x releases. But if you manually upgrade to 7.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.