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 ember-resolver is breaking the build 🚨 #93

Open
greenkeeper bot opened this issue Sep 24, 2019 · 1 comment
Open

An in-range update of ember-resolver is breaking the build 🚨 #93

greenkeeper bot opened this issue Sep 24, 2019 · 1 comment

Comments

@greenkeeper
Copy link

greenkeeper bot commented Sep 24, 2019

The devDependency ember-resolver was updated from 5.2.1 to 5.3.0.

🚨 View failing branch.

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

ember-resolver 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).

Release Notes for Release 5.3.0

v5.3.0 (2019-09-24)

🚀 Enhancement

  • #417 Add support for nested colocated components. (@rwjblue)

Committers: 1

Commits

The new version differs by 8 commits.

  • 56e4304 Release 5.3.0
  • fd8701e Add support for nested colocated components. (#417)
  • 28ef51e Add resolution for engine.io.
  • a2be8db Upgrade to xenial
  • e63891d Add support for nested colocated components.
  • 98dc24f [Security] Bump mixin-deep from 1.3.1 to 1.3.2
  • 2b698fe Bump ember-load-initializers from 2.0.0 to 2.1.0
  • f7e4237 [Security] Bump eslint-utils from 1.3.1 to 1.4.2

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 Sep 24, 2019

After pinning to 5.2.1 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