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

An in-range update of npm-run-all is breaking the build 🚨 #105

Open
greenkeeper bot opened this issue Aug 26, 2017 · 6 comments
Open

An in-range update of npm-run-all is breaking the build 🚨 #105

greenkeeper bot opened this issue Aug 26, 2017 · 6 comments

Comments

@greenkeeper
Copy link

greenkeeper bot commented Aug 26, 2017

Version 4.1.0 of npm-run-all just got published.

Branch Build failing 🚨
Dependency npm-run-all
Current Version 4.0.2
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As npm-run-all is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Status Details
  • continuous-integration/travis-ci/push The Travis CI build is in progress Details
  • continuous-integration/appveyor/branch AppVeyor build failed Details

Release Notes v4.1.0

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.
Commits

The new version differs by 14 commits.

  • 59219e8 4.1.0
  • f7f7b43 Fix: MaxListenersExceededWarning (fixes #105)
  • 64f6479 Chore: use async/await in tests
  • 66fa8ff Chore: upgrade dependencies
  • 8c8bec0 Docs: update docs
  • 8c6debf Chore: tweak CI settings
  • 5fcc2c6 Chore: no package-lock
  • e07e782 New: add --aggregate-output option (fixes #36)(#104)
  • dff6409 Docs: add note about Yarn compatibility (#103)
  • 94f1b64 Merge pull request #101 from ntwb/patch-1
  • a8364ce Add Node.j 8.x to AppVeyor CI
  • c6d3092 Add Node.js 8.x to Travis CI
  • 873f036 Merge pull request #95 from goto-bus-stop/feature/docs-in-pkg
  • 0fca0e0 Include docs in published npm package.

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

@greenkeeper
Copy link
Author

greenkeeper bot commented Aug 26, 2017

After pinning to 4.0.2 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.

@greenkeeper
Copy link
Author

greenkeeper bot commented Aug 28, 2017

Version 4.1.1 just got published.

Your tests are still failing with this version. Compare the changes 🚨

Commits

The new version differs by 3 commits.

  • 7e83545 4.1.1
  • ac9358a Chore: configure appveyor to run on only Node 8.
  • fbd4024 Fix: Use ansi-style directly instead of chalk.styles (#108)

See the full diff

@greenkeeper
Copy link
Author

greenkeeper bot commented Nov 7, 2017

Version 4.1.2 just got published.

Your tests are still failing with this version. Compare the changes 🚨

Release Notes v4.1.2

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...43a6b16 fixed the problem with using yarn (#113).
Commits

The new version differs by 8 commits.

  • ec4d56c 4.1.2
  • cc8611c Chore: upgrade dependencies
  • 43a6b16 Chore: fix tests
  • dfb9dcb Fix: fix for latest yarn
  • 528d105 Chore: trivial fix
  • 693261b Fix: missing --aggregate-output in npm-run-all
  • 096779b Fix: --aggregate-output cannot handle large data (fixes #111)(#112)
  • 6ef64ab Chore: add Node 9 to Travis CI

See the full diff

@greenkeeper
Copy link
Author

greenkeeper bot commented May 6, 2018

Version 4.1.3 just got published.

Your tests are still failing with this version. Compare the changes 🚨

Commits

The new version differs by 6 commits.

  • 52eaf86 4.1.3
  • 61bad5c Chore: upgrade dependencies
  • 35f86ae Fix: unexpected behavior of leading bang (#124)
  • c76db0e Docs: typo fix in README.md: is/are (#120)
  • d56c268 Fix: colorize tasks names sequentially instead of by hash (#115)
  • 21c0269 Chore: trivial fix

See the full diff

@greenkeeper
Copy link
Author

greenkeeper bot commented Nov 24, 2018

  • The devDependency npm-run-all was updated from 4.1.3 to 4.1.4.

Your tests are still failing with this version. Compare changes

Commits

The new version differs by 3 commits.

See the full diff

@greenkeeper
Copy link
Author

greenkeeper bot commented Nov 24, 2018

  • The devDependency npm-run-all was updated from 4.1.4 to 4.1.5.

Your tests are still failing with this version. Compare changes

Commits

The new version differs by 5 commits.

  • df15118 🔖 4.1.5
  • 94007fd ⚒ make test's timeout longer
  • 1b41ac5 🐛 use pidtree
  • 7ec542e ⬆️ update dependencies
  • 51e678e Revert: "remove test in version script temporary"

See the full diff

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

No branches or pull requests

0 participants