Update dependency concurrently to v10

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
concurrently	9.2.1 → 10.0.3

---

Release Notes

open-cli-tools/concurrently (concurrently)

v10.0.3

Compare Source

Republish of https://github.com/open-cli-tools/concurrently/releases/tag/v10.0.1 with Trusted Publishing enabled (see #​595)

Full Changelog: open-cli-tools/concurrently@v10.0.2...v10.0.3

v10.0.1

Compare Source

• Ensure FlowController type is exported - #​594

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

v10.0.0

Compare Source

💥 Breaking Changes

• Dropped support for Node.js <22.0.0.
  Older Node.js version have reached end-of-life, and certain features require new-ish JS APIs.
• concurrently is now ESM-only.
  It's now possible to require(esm). See here for interoperability.
• Prefix colors now default to automatic - #​581
  The colors used to default to reset (which does nothing). Concurrently now automatically selects a color, out of the box.
  The list of colors used is not jarring nor carries semantic meaning, and reads well in both dark and light terminal backgrounds.
• Removed deprecated flags and options
  • CLI flag --name-separator: use commas instead.
  • API option killOthers: use killOthersOn instead.

✨ New Features

• Support applying modifiers to hex prefix colors (e.g. #ff0000.bold) - #​450
• Support chalk's color functions in prefixes (e.g. rgb(), hex(), bgRgb(), etc) - #​578
• Set prefix background color via bg#RRGGBB - #​578
• Allow shell override via --shell CLI flag/shell API option - #​288, #​589, #​556
  concurrently distinguishes between cmd.exe, powershell, and POSIX-based shells.
• Manual prefix coloring in templates e.g. [{color}{name}{/color}] - #​583, #​587

🐛 Bug fixes

• Scope quote normalization to CLI input - #​582, #​585
  It should now also be possible to run commands like "/some/command" foo bar"
• Don't throw when color doesn't exist - #​580

🔐 Security

• Address vulnerability in shellquote - #​591

Other changes

• Warn about running on Snap - #​584

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: (UTC)

• 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 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: package-lock.json

npm warn Unknown env config "store". This will stop working in the next major version of npm. See `npm help npmrc` for supported config options.
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @eslint/js@10.0.1
npm error Found: eslint@9.39.2
npm error node_modules/eslint
npm error   dev eslint@"^9.39.2" from the root project
npm error   peer eslint@"^7.5.0 || ^8.0.0 || ^9.0.0" from @babel/eslint-parser@7.28.6
npm error   node_modules/@babel/eslint-parser
npm error     dev @babel/eslint-parser@"^7.28.6" from the root project
npm error   7 more (@eslint-community/eslint-utils, @eslint/compat, ...)
npm error
npm error Could not resolve dependency:
npm error peerOptional eslint@"^10.0.0" from @eslint/js@10.0.1
npm error node_modules/@eslint/js
npm error   dev @eslint/js@"^10.0.1" from the root project
npm error
npm error Conflicting peer dependency: eslint@10.4.1
npm error node_modules/eslint
npm error   peerOptional eslint@"^10.0.0" from @eslint/js@10.0.1
npm error   node_modules/@eslint/js
npm error     dev @eslint/js@"^10.0.1" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry this command with --force or --legacy-peer-deps to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /runner/cache/others/npm/_logs/2026-06-02T05_26_12_070Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-06-02T05_26_12_070Z-debug-0.log