Skip to content

build: update dependency concurrently to v9 #31149

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
May 20, 2025

Conversation

angular-robot
Copy link
Collaborator

This PR contains the following updates:

Package Type Update Change
concurrently devDependencies major ^7.0.0 -> ^9.0.0

Release Notes

open-cli-tools/concurrently (concurrently)

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 - "after 10:00pm every weekday,before 5:00am every weekday,every weekend" in timezone America/Tijuana, 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.

See associated pull request for more information.
@angular-robot angular-robot requested a review from a team as a code owner May 19, 2025 19:44
@angular-robot angular-robot requested review from wagnermaciel and removed request for a team May 19, 2025 19:44
@angular-robot angular-robot added the action: merge The PR is ready for merge by the caretaker label May 19, 2025
@angular-robot angular-robot requested a review from ok7sai May 19, 2025 19:44
@angular-robot angular-robot added the area: build & ci Related the build and CI infrastructure of the project label May 19, 2025
@alan-agius4 alan-agius4 added the target: rc This PR is targeted for the next release-candidate label May 19, 2025
@mmalerba mmalerba merged commit 30df8d3 into angular:main May 20, 2025
29 checks passed
@mmalerba
Copy link
Contributor

The changes were merged into the following branches: main, 20.0.x

mmalerba pushed a commit that referenced this pull request May 20, 2025
See associated pull request for more information.

(cherry picked from commit 30df8d3)
@angular-robot angular-robot deleted the ng-renovate/concurrently-9-x branch May 20, 2025 23:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
action: merge The PR is ready for merge by the caretaker area: build & ci Related the build and CI infrastructure of the project target: rc This PR is targeted for the next release-candidate
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants