This version is covered by your current version range and after updating it in your project the build failed.
As es6-promise 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** CircleCI is running your tests [Details](https://circleci.com/gh/issuemd/issue.md/89?utm_campaign=vcs-integration-link&utm_medium=referral&utm_source=github-build-link)
- β **bitHound - Dependencies** No failing dependencies. [Details](https://www.bithound.io/github/issuemd/issue.md/bc22f8abb44d5b0013d92977f7627c57f221fa41/dependencies/npm?status=passing)
- β **bitHound - Code** 2 failing files. [Details](https://www.bithound.io/github/issuemd/issue.md/bc22f8abb44d5b0013d92977f7627c57f221fa41/files#filter-failing-file)
Commits
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).
After pinning to 4.1.0 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.
Version 4.1.1 of es6-promise just got published.
This version is covered by your current version range and after updating it in your project the build failed.
As es6-promise 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** CircleCI is running your tests [Details](https://circleci.com/gh/issuemd/issue.md/89?utm_campaign=vcs-integration-link&utm_medium=referral&utm_source=github-build-link) - β **bitHound - Dependencies** No failing dependencies. [Details](https://www.bithound.io/github/issuemd/issue.md/bc22f8abb44d5b0013d92977f7627c57f221fa41/dependencies/npm?status=passing) - β **bitHound - Code** 2 failing files. [Details](https://www.bithound.io/github/issuemd/issue.md/bc22f8abb44d5b0013d92977f7627c57f221fa41/files#filter-failing-file)Commits
The new version differs by 25 commits.
7f82a56
release v4.1.1 π
8a9da19
update dist
f046478
Merge pull request #295 from bekzod/remove-object-equals
3618c88
Merge pull request #296 from bekzod/fix-catch
f6a08f4
calling
.catch
directly and removedkeysOf
083ff55
remove
objectEquals
476838e
Merge pull request #294 from bekzod/dont-use-input
f496839
don't store input in
enumerator
10a6859
Merge pull request #288 from bekzod/small-util-cleanup
b844617
small cleanup in util
b37a3d0
Merge pull request #283 from stefanpenner/greenkeeper-ember-cli-2.12.2
9da2db5
Merge pull request #284 from bradoyler/patch-1
7266c29
fix npm SEO for 'promise polyfill'
9a207cf
chore(package): update ember-cli to version 2.12.2
e483c20
Merge pull request #280 from stefanpenner/greenkeeper-release-it-2.7.1
There are 25 commits in total.
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: