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 broccoli-persistent-filter is breaking the build 🚨 #43

Open
greenkeeper bot opened this issue Jun 26, 2017 · 4 comments
Open

Comments

@greenkeeper
Copy link

greenkeeper bot commented Jun 26, 2017

Version 1.4.0 of broccoli-persistent-filter just got published.

Branch Build failing 🚨
Dependency broccoli-persistent-filter
Current Version 1.3.1
Type devDependency

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

As broccoli-persistent-filter 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 failed Details

Commits

The new version differs by 39 commits.

  • 15c4d49 release v1.4.0 🎉
  • ce27a35 Merge pull request #111 from mikrostew/master
  • 3d5036b address feedback
  • 0376fb7 pull the worker function out
  • b5335d3 cleanup throttling tests
  • 5f02570 fix async build failure test
  • ad61a3a Merge remote-tracking branch 'upstream/master'
  • acff68a fix throttling so it works correctly
  • 21f70d7 Merge pull request #114 from stefanpenner/greenkeeper/chai-as-promised-7.0.0
  • 61532e5 chore(package): update chai-as-promised to version 7.0.0
  • b1b1cdd update where concurrency is set and add tests
  • c5a2bd1 add configurable concurrency
  • 39bbfed Revert "configurable concurrency, and simplify applyPatches section"
  • 59d323f configurable concurrency, and simplify applyPatches section
  • 4c89193 report heimdall stats correctly for async work

There are 39 commits in total.

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 Jun 26, 2017

After pinning to 1.3.1 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 Jun 29, 2017

Version 1.4.1 just got published.

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

Commits

The new version differs by 3 commits.

  • d2c1bbc release vv1.4.1 🎉
  • 73745e3 Merge pull request #115 from mikrostew/compatibility-fix
  • 6687cc9 change ES6 -> ES5 syntax

See the full diff

@greenkeeper
Copy link
Author

greenkeeper bot commented Jun 30, 2017

Version 1.4.2 just got published.

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

Commits

The new version differs by 7 commits.

  • 3ab5d8f release v1.4.2 🎉
  • 57d8f90 Merge pull request #116 from mikrostew/use-es5
  • 0981151 omg CI is so slow for these
  • 8656b30 fix test timeout
  • b1212fe bump async-promise-queue dependency + whitelist
  • e7ac9a3 run tests using node 0.12
  • c763463 inline md5-hex and convert it to ES5

See the full diff

@greenkeeper
Copy link
Author

greenkeeper bot commented Aug 15, 2017

Version 1.4.3 just got published.

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

Commits

The new version differs by 3 commits.

  • d0bcc3f release v1.4.3 🎉
  • 209d27a Merge pull request #128 from blimmer/remove-crypto-package
  • 6aacdfd Remove crypto package.

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