search

kellyselden / ember-cli-tree-shaker

Experiment with tree-shaking in Ember CLI
MIT License
76 stars 7 forks source link

An in-range update of broccoli-funnel is breaking the build 🚨 #72

Open greenkeeper[bot] opened 5 years ago

greenkeeper[bot] commented 5 years ago

The dependency broccoli-funnel was updated from 2.0.1 to 2.0.2.

🚨 View failing branch.

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

broccoli-funnel is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details - ❌ **continuous-integration/travis-ci/push:** The Travis CI build failed ([Details](https://travis-ci.org/kellyselden/ember-cli-tree-shaker/builds/490598305?utm_source=github_status&utm_medium=notification)).
Commits

The new version differs by 14 commits.

  • fc12aaf Remove broken auto-publishing via preversion/postversion scripts
  • 87c784d v2.0.2
  • 48960a4 Add v2.0.2 to CHANGELOG.md.
  • 00de4f4 Merge pull request #106 from chriskrycho/input-node-105
  • a793c0b Fix indentation in latest-added test.
  • 6f031e3 Add test for creating nested output when missing input node.
  • 67b2e2c Make an empty dir if missing but allowEmpty.
  • 74f3454 Add test for available input node at missing source.
  • a76c4ee Handle empty src dir if allowEmpty with include/exclude.
  • c49cf8d Add failing test for include/exclude and empty input node.
  • bfea8d4 Merge pull request #102 from davewasmer/patch-1
  • 0afbb9c Fix exclude option docs
  • 0859618 Merge pull request #101 from reidab/patch-1
  • bfdd055 Update changelog for recent releases

See the full diff

FAQ and help There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those don’t help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).

Your Greenkeeper Bot :palm_tree:

greenkeeper[bot] commented 5 years ago

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