Skip to content
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

Update dependency npm-run-all to v4.1.5 #25

Merged
merged 1 commit into from
Jan 9, 2024

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jan 3, 2024

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
npm-run-all 4.0.2 -> 4.1.5 age adoption passing confidence

Release Notes

mysticatea/npm-run-all (npm-run-all)

v4.1.5

Compare Source

🐛 Bug fixes

  • 52eaf86...1b41ac569987c96e224f940ff59f9699322c7824 switched ps-tree package to pidtree package for security reason.

v4.1.4

Compare Source

v4.1.3

Compare Source

🐛 Bug fixes

  • d56c268 improved label colors
  • 35f86ae fixed a bug that the script name which starts with ! makes npm-run-all confusing.

v4.1.2

Compare Source

Bug fixes

  • 096779b fixed the problem that --aggregate-output option does not work if child tasks print large output (#​111). Thank you, @​jlopezxs!
  • 693261b fixed the problem that --aggregate-output option does not work on npm-run-all command.
  • 528d105...43a6b1683374e3dd314733ec5559908abfcc6cd1 fixed the problem with using yarn (#​113).

v4.1.1

Compare Source

Bug fixes

  • fbd4024 fixed a regression bug of --print-name.

v4.1.0

Compare Source

Features

  • e07e782 add --aggregate-output option. This option avoids that the output of tasks is mixed even if parallel mode. Don't use this option if a task never finishes (e.g. web server, file watching, ...).
    Thank you, @​fatso83 !

Bug fixes

  • f7f7b43 fixed a bug that npm-run-all shows MaxListenersExceededWarning warnings if it runs many tasks in parallel.

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 has been generated by Mend Renovate. View repository job log here.

@renovate renovate bot force-pushed the renovate/npm-run-all-4.x-lockfile branch 2 times, most recently from 3cfd101 to 48df59b Compare January 9, 2024 16:30
@renovate renovate bot force-pushed the renovate/npm-run-all-4.x-lockfile branch from 48df59b to 3d87198 Compare January 9, 2024 16:31
@masarakki masarakki merged commit 50a5baa into master Jan 9, 2024
1 check passed
@masarakki masarakki deleted the renovate/npm-run-all-4.x-lockfile branch January 9, 2024 17:28
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.

1 participant