An in-range update of ember-percy is breaking the build 🚨

[greenkeeper[bot]]

Version 1.2.17 of ember-percy just got published.

Branch	Build failing 🚨
Dependency	ember-percy
Current Version	1.2.16
Type	devDependency

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

As ember-percy 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

- ❌ **continuous-integration/travis-ci/push** The Travis CI build is in progress [Details](https://travis-ci.org/kellyselden/package-hint-historic-resolver/builds/276937986?utm_source=github_status&utm_medium=notification) - ❌ **percy/package-hint-historic-resolver** Missing build resources, check your CI logs for failures [Details](https://percy.io/kellyselden/package-hint-historic-resolver/builds/345401)

---

Commits

The new version differs by 3 commits.

• 9a3d458 Version 1.2.17
• 49fb96a Support ember test using a pre-built app (#44)
• a0f20b5 Setup Windows CI (#42)

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]]

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

[greenkeeper[bot]]

Version 1.2.18 just got published.

Your tests are passing again with this version. Explicitly upgrade to this version 🚀