Skip to content

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

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Sep 9, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
concurrently 7.6.0 -> 9.2.0 age adoption passing confidence

Release Notes

open-cli-tools/concurrently (concurrently)

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 12:00 AM through 04:59 AM and 10:00 PM through 11:59 PM, Monday through Friday ( * 0-4,22-23 * * 1-5 ), Only on Sunday and Saturday ( * * * * 0,6 ) in timezone Asia/Manila, 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 from 898f29d to 4072594 Compare September 12, 2024 01:14
@renovate renovate bot force-pushed the renovate/concurrently-9.x branch 2 times, most recently from 98d12ec to f68cffd Compare November 4, 2024 13:04
@renovate renovate bot changed the title chore(deps): update dependency concurrently to v9 chore(deps): update dependency concurrently to v9 - autoclosed Dec 8, 2024
@renovate renovate bot closed this Dec 8, 2024
@renovate renovate bot deleted the renovate/concurrently-9.x branch December 8, 2024 18:59
@renovate renovate bot changed the title chore(deps): update dependency concurrently to v9 - autoclosed chore(deps): update dependency concurrently to v9 Dec 13, 2024
@renovate renovate bot reopened this Dec 13, 2024
@renovate renovate bot force-pushed the renovate/concurrently-9.x branch 2 times, most recently from f68cffd to 06fbea0 Compare December 14, 2024 00:20
@renovate renovate bot force-pushed the renovate/concurrently-9.x branch 2 times, most recently from c8091fa to f69181b Compare December 31, 2024 06:45
@renovate renovate bot force-pushed the renovate/concurrently-9.x branch from f69181b to 758ebbe Compare June 22, 2025 08:24
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