search

iamstarkov / travis-config-keys

Travis configs properties in correct order
1 stars 0 forks source link

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

Closed greenkeeper[bot] closed 6 years ago

greenkeeper[bot] commented 7 years ago

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 :muscle:

Status Details - ❌ **continuous-integration/travis-ci/push** The Travis CI build could not complete due to an error [Details](https://travis-ci.org/iamstarkov/travis-config-keys/builds/268680175?utm_source=github_status&utm_medium=notification)
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](https://greenkeeper.io/faq.html) and of course you may always [ask my humans](https://github.com/greenkeeperio/greenkeeper/issues/new).

Your Greenkeeper Bot :palm_tree:

greenkeeper[bot] commented 7 years ago

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[bot] commented 7 years ago

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