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 loader.js is breaking the build 🚨 #291

Open
greenkeeper bot opened this issue Apr 11, 2018 · 1 comment
Open

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

greenkeeper bot opened this issue Apr 11, 2018 · 1 comment

Comments

@greenkeeper
Copy link

greenkeeper bot commented Apr 11, 2018

☝️ 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
  • continuous-integration/travis-ci/push The Travis CI build failed Details

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. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

@greenkeeper
Copy link
Author

greenkeeper bot commented Apr 11, 2018

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.

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