bmeurant / ember-array-contains-helper

Ember helper to test the presence of a value in an array
http://bmeurant.github.io/ember-array-contains-helper/
MIT License
21 stars 2 forks source link

An in-range update of loader.js is breaking the build 🚨 #150

Closed greenkeeper[bot] closed 6 years ago

greenkeeper[bot] commented 6 years ago

☝️ Greenkeeper’s updated Terms of Service will come into effect on April 6th, 2018.

Version 4.7.0 of loader.js was just published.

Branch Build failing 🚨
Dependency loader.js
Current Version 4.6.0
Type devDependency

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

loader.js is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details - ❌ **coverage/coveralls** Coverage pending from Coveralls.io [Details](https://coveralls.io/builds/16467780) - ❌ **continuous-integration/travis-ci/push** The Travis CI build failed [Details](https://travis-ci.org/bmeurant/ember-array-contains-helper/builds/365270079?utm_source=github_status&utm_medium=notification)

Commits

The new version differs by 9 commits.

  • 27b4098 release v4.7.0 🎉
  • d42a2c7 Merge pull request #137 from 2hu12/patch-1
  • 367dbfc Update define.alias API description
  • d5fb086 Merge pull request #133 from tmquinn/find-alias-modules-with-index
  • ffacdb4 Add test for quz/index
  • 933c7c8 Merge pull request #134 from ember-cli/add-test
  • ed8c85a Fix typo and add tests
  • 5141a0f Add test ensuring /index doesn’t invokes callbacks the appropriate number of times
  • f8b282b Find aliases whose target is at index

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 6 years ago

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

bmeurant commented 6 years ago

Closing. False negative.

See: