Skip to content

chore(deps): update dependency concurrently to v9#74

Open
renovate[bot] wants to merge 1 commit intomainfrom
renovate/concurrently-9.x
Open

chore(deps): update dependency concurrently to v9#74
renovate[bot] wants to merge 1 commit intomainfrom
renovate/concurrently-9.x

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate bot commented Apr 29, 2025

This PR contains the following updates:

Package Change Age Confidence
concurrently ^7.4.0^9.0.0 age confidence

Release Notes

open-cli-tools/concurrently (concurrently)

v9.2.1

Compare Source

What's Changed

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

v9.2.0

Compare Source

What's Changed

New Contributors

Full Changelog: open-cli-tools/concurrently@v9.1.2...v9.2.0

v9.1.2

Compare Source

What's Changed

New Contributors

Full Changelog: open-cli-tools/concurrently@v9.1.1...v9.1.2

v9.1.1

Compare Source

What's Changed

Full Changelog: open-cli-tools/concurrently@v9.1.0...v9.1.1

v9.1.0

Compare Source

What's Changed

New Contributors

Full Changelog: open-cli-tools/concurrently@v9.0.1...v9.1.0

v9.0.1

Compare Source

What's Changed

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

v9.0.0

Compare Source

💥 Breaking Changes

  • Dropped support for Node.js < 18.0.0.
    Older Node.js version have reached end-of-life, and certain features require new-ish JS APIs.

  • Pending commands no longer run when --max-processes is set and an interruption/kill signal is sent - #​433, #​452, #​460
    Before v9.0.0, pressing Ctrl+C when --max-processes is set meant that only those commands would receive it. Once these stopped, the pending commands would start, which in turn meant that another Ctrl+C press would be necessary to stop them, and so on.
    Similar situation applied to combining --max-processes with --kill-others/--kill-others-on-fail.

    Starting with v9.0.0, this no longer happens, as these flags and/or key presses send a signal to stop the running commands in addition to preventing new commands from running.

  • The concurrently and default exports are now the same - #​399
    It's reasonable to expect that import { concurrently } from 'concurrently' would work the same as import concurrently from 'concurrently', however this has not been the case.
    The former used to be an unconfigured version of concurrently, lacking all features that you'd get from the CLI, which was seen as a "footgun". Both are now the same function.

    If you'd like to access the unconfigured function, use import { createConcurrently } from 'concurrently' instead.

✨ New Features

  • Exponential back-off support for process restarting - #​265, #​462
    Use --restart-after exponential. Restarts happen at 2^N seconds.
  • Add prefix padding via new --pad-prefix flag - #​166, #​417, #​495
  • Specify teardown commands via new --teardown flag - #​472, #​500
  • Expand node:<script> commands to node --run <script> - #​475
  • [API only] Inter-Process Communication (ipc) - #​498
  • [API only] Make it possible to use no colors at all - #​466
  • [API only] Add a state field to Command - #​455

🐛 Bug Fixes

Other Changes

New Contributors

Full Changelog: open-cli-tools/concurrently@v8.2.2...v9.0.0

v8.2.2

Compare Source

What's Changed

New Contributors

Full Changelog: open-cli-tools/concurrently@v8.2.1...v8.2.2

v8.2.1

Compare Source

What's Changed

New Contributors

Full Changelog: open-cli-tools/concurrently@v8.2.0...v8.2.1

v8.2.0

Compare Source

What's Changed

New Contributors

Full Changelog: open-cli-tools/concurrently@v8.1.0...v8.2.0

v8.1.0

Compare Source

What's Changed

New Contributors

Full Changelog: open-cli-tools/concurrently@v8.0.1...v8.1.0

v8.0.1

Compare Source

What's Changed

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

v8.0.0

Compare Source

What's Changed

New Contributors

Full Changelog: open-cli-tools/concurrently@v7.6.0...v8.0.0


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 was generated by Mend Renovate. View the repository job log.

@coderabbitai
Copy link
Copy Markdown

coderabbitai bot commented Apr 29, 2025

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.


Comment @coderabbitai help to get the list of available commands and usage tips.

@renovate renovate bot force-pushed the renovate/concurrently-9.x branch from fee19a5 to 26f4174 Compare August 10, 2025 12:39
@renovate renovate bot force-pushed the renovate/concurrently-9.x branch 2 times, most recently from 1294459 to fcdc100 Compare August 25, 2025 10:11
@renovate renovate bot force-pushed the renovate/concurrently-9.x branch from fcdc100 to b40229a Compare August 31, 2025 09:43
@renovate renovate bot force-pushed the renovate/concurrently-9.x branch from b40229a to 5436658 Compare December 31, 2025 17:33
@renovate renovate bot force-pushed the renovate/concurrently-9.x branch from 5436658 to 9b61032 Compare January 8, 2026 19:00
@renovate renovate bot force-pushed the renovate/concurrently-9.x branch from 9b61032 to 4004ec5 Compare January 23, 2026 17:33
@renovate
Copy link
Copy Markdown
Contributor Author

renovate bot commented Jan 23, 2026

⚠️ 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 ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: @fastify/type-provider-typebox@2.3.0
npm ERR! Found: @sinclair/typebox@0.34.47
npm ERR! node_modules/@sinclair/typebox
npm ERR!   @sinclair/typebox@"^0.34.0" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer @sinclair/typebox@"^0.24.1" from @fastify/type-provider-typebox@2.3.0
npm ERR! node_modules/@fastify/type-provider-typebox
npm ERR!   @fastify/type-provider-typebox@"^2.3.0" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: @sinclair/typebox@0.24.51
npm ERR! node_modules/@sinclair/typebox
npm ERR!   peer @sinclair/typebox@"^0.24.1" from @fastify/type-provider-typebox@2.3.0
npm ERR!   node_modules/@fastify/type-provider-typebox
npm ERR!     @fastify/type-provider-typebox@"^2.3.0" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /runner/cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /runner/cache/others/npm/_logs/2026-03-13T10_51_33_226Z-debug-0.log

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants