search

echobind / ember-links-with-follower

Render a set of links with a "follower" line underneath. The follower moves to the active link, matching size and position on the page.
https://echobind.github.io/ember-links-with-follower
MIT License
45 stars 2 forks source link

An in-range update of broccoli-asset-rev is breaking the build 🚨 #213

Closed greenkeeper[bot] closed 6 years ago

greenkeeper[bot] commented 7 years ago

Version 2.6.0 of broccoli-asset-rev just got published.

Branch Build failing 🚨
Dependency broccoli-asset-rev
Current Version 2.5.0
Type devDependency

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

As broccoli-asset-rev 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 - ❌ **ci/circleci** Your tests failed on CircleCI [Details](https://circleci.com/gh/echobind/ember-links-with-follower/310?utm_campaign=vcs-integration-link&utm_medium=referral&utm_source=github-build-link)
Commits

The new version differs by 8 commits.

  • e5ee2bc 2.6.0
  • 5cfdfaa Merge pull request #121 from RevolutionDisplay/two-stage
  • 433ced7 revert non-glob string exclusions to a substring search + unit test
  • 684c5ee extend basic test to verify .json files are different from .js #118
  • a9484bf extensions must match at the end of a string #118
  • cd54cd8 update filter-tests to explicitly read files using null encoding
  • 3d7b727 avoid es6 methods (node 0.12 friendly)
  • c41494c split fingerprint + rewrite into two stages to address #118

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 2.5.0 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.