Skip to content

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

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

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

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate Bot commented Sep 8, 2024

This PR contains the following updates:

Package Change Age Confidence
concurrently ^8.2.2^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


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 renovate Bot force-pushed the renovate/concurrently-9.x branch 2 times, most recently from 81bed03 to 981a8a1 Compare September 30, 2024 07:16
@renovate renovate Bot force-pushed the renovate/concurrently-9.x branch from 981a8a1 to 5d319a8 Compare October 9, 2024 01:48
@renovate renovate Bot force-pushed the renovate/concurrently-9.x branch from 5d319a8 to 8171a91 Compare August 10, 2025 14:55
@renovate renovate Bot force-pushed the renovate/concurrently-9.x branch 2 times, most recently from d5218da to 87e59d8 Compare August 25, 2025 15:23
@renovate renovate Bot force-pushed the renovate/concurrently-9.x branch from 87e59d8 to e6c5665 Compare September 25, 2025 15:03
@renovate renovate Bot force-pushed the renovate/concurrently-9.x branch from e6c5665 to 54e0bac Compare November 10, 2025 17:45
@renovate renovate Bot force-pushed the renovate/concurrently-9.x branch from 54e0bac to 650af7f Compare December 31, 2025 16:03
@renovate renovate Bot force-pushed the renovate/concurrently-9.x branch from 650af7f to 619658e Compare January 19, 2026 16:12
@renovate renovate Bot force-pushed the renovate/concurrently-9.x branch from 619658e to b0f1b71 Compare February 2, 2026 21:11
@renovate renovate Bot force-pushed the renovate/concurrently-9.x branch from b0f1b71 to 950a744 Compare February 12, 2026 17:37
@renovate renovate Bot force-pushed the renovate/concurrently-9.x branch from 950a744 to 30fb05e Compare March 5, 2026 16:08
@renovate renovate Bot force-pushed the renovate/concurrently-9.x branch from 30fb05e to eb5ef9c Compare April 29, 2026 19:40
@renovate renovate Bot force-pushed the renovate/concurrently-9.x branch from eb5ef9c to f0f9401 Compare May 12, 2026 16:19
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