chore(deps): update dependency concurrently to v10

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
concurrently	^9.1.0 → ^10.0.0
concurrently	^9.0.0 → ^10.0.0

---

Release Notes

open-cli-tools/concurrently (concurrently)

v10.0.0

Compare Source

What's Changed

• Rename killOthers to killOthersOn in README example by @​philfreo in #​566
• Clarify usage of makeTests() by @​gustavohenke in #​567
• Support hex prefix colors with modifiers by @​garretmh in #​450
• Drop support for Node.js 18, add support for Node.js 24 by @​paescuj in #​565
• ESM only by @​gustavohenke in #​568
• Cleanups by @​paescuj in #​570
• Update deps by @​paescuj in #​571
• Rename src to lib by @​paescuj in #​572
• Correct modifier application description in prefixing.md by @​CodeF53 in #​574
• [Readme] add note about windows only supporting double quotes by @​nkappler in #​577
• feat: add support for Chalk color functions in prefix colors by @​stephanschubert in #​578
• feat: enable automatic prefix colors by default by @​GermanJablo in #​581
• Allow shell overrides by @​gustavohenke in #​589
• feat: coloring prefixes by @​y-nk in #​587
• deps: Upgrade shell-quote to 1.8.4 by @​samchungy in #​591
• docs: update outdated Node.js doc links and fix null code formatting by @​saito-netartz in #​590
• fix: scope quote normalization to CLI input by @​jeffrey-takuma in #​585
• deps: upgrade yargs to v18 by @​gustavohenke in #​593

New Contributors

• @​philfreo made their first contribution in #​566
• @​garretmh made their first contribution in #​450
• @​CodeF53 made their first contribution in #​574
• @​nkappler made their first contribution in #​577
• @​stephanschubert made their first contribution in #​578
• @​GermanJablo made their first contribution in #​581
• @​y-nk made their first contribution in #​587
• @​samchungy made their first contribution in #​591
• @​saito-netartz made their first contribution in #​590
• @​jeffrey-takuma made their first contribution in #​585

Full Changelog: open-cli-tools/concurrently@v9.2.1...v10.0.0

---

Configuration

📅 Schedule: (in timezone America/New_York)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • "after 10pm every weekday,before 5am every weekday,every weekend"

🚦 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 these updates again.

---

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

---

This PR was generated by Mend Renovate. View the repository job log.

[renovate]

⚠️ 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

Scope: all 2 workspace projects
? Verifying lockfile against supply-chain policies (2201 entries)...
✗ Lockfile failed supply-chain policy check (2201 entries in 8.9s)
[ERR_PNPM_MINIMUM_RELEASE_AGE_VIOLATION] 13 lockfile entries failed verification:
  @sentry-internal/browser-utils@10.55.0 was published at 2026-05-28T13:55:18.205Z, within the minimumReleaseAge cutoff (2026-05-28T00:45:31.529Z)
  @sentry-internal/feedback@10.55.0 was published at 2026-05-28T13:55:25.805Z, within the minimumReleaseAge cutoff (2026-05-28T00:45:31.529Z)
  @sentry-internal/replay-canvas@10.55.0 was published at 2026-05-28T13:55:27.994Z, within the minimumReleaseAge cutoff (2026-05-28T00:45:31.529Z)
  @sentry-internal/replay@10.55.0 was published at 2026-05-28T13:55:21.154Z, within the minimumReleaseAge cutoff (2026-05-28T00:45:31.529Z)
  @sentry/browser@10.55.0 was published at 2026-05-28T13:55:31.823Z, within the minimumReleaseAge cutoff (2026-05-28T00:45:31.529Z)
  @sentry/core@10.55.0 was published at 2026-05-28T13:55:11.085Z, within the minimumReleaseAge cutoff (2026-05-28T00:45:31.529Z)
  @sentry/nextjs@10.55.0 was published at 2026-05-28T13:56:17.103Z, within the minimumReleaseAge cutoff (2026-05-28T00:45:31.529Z)
  @sentry/node-core@10.55.0 was published at 2026-05-28T13:55:15.651Z, within the minimumReleaseAge cutoff (2026-05-28T00:45:31.529Z)
  @sentry/node@10.55.0 was published at 2026-05-28T13:55:36.202Z, within the minimumReleaseAge cutoff (2026-05-28T00:45:31.529Z)
  @sentry/opentelemetry@10.55.0 was published at 2026-05-28T13:55:23.412Z, within the minimumReleaseAge cutoff (2026-05-28T00:45:31.529Z)
  @sentry/profiling-node@10.55.0 was published at 2026-05-28T13:55:37.984Z, within the minimumReleaseAge cutoff (2026-05-28T00:45:31.529Z)
  @sentry/react@10.55.0 was published at 2026-05-28T13:55:46.473Z, within the minimumReleaseAge cutoff (2026-05-28T00:45:31.529Z)
  @sentry/vercel-edge@10.55.0 was published at 2026-05-28T13:55:55.876Z, within the minimumReleaseAge cutoff (2026-05-28T00:45:31.529Z)

The lockfile contains entries that the active policies reject. This can mean the lockfile is stale, or that someone committed a lockfile that bypassed the policy locally — inspect recent changes to pnpm-lock.yaml before trusting it. If the changes look expected, run "pnpm clean --lockfile" and then "pnpm install" to rebuild from a fresh resolution. Alternatively, relax the policy that flagged them.