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

[greenkeeper]

Version 2.10.0 of ember-data just got published.

Branch	Build failing 🚨
Dependency	ember-data
Current Version	2.9.0
Type	devDependency

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

As ember-data 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 💪

---

Status Details

• ❌ continuous-integration/travis-ci/push The Travis CI build failed Details

Commits

The new version differs by 65 commits (ahead by 65, behind by 25).

• bda9732 Release Ember Data 2.10.0
• a22a702 Update changelog for the Ember Data 2.10.0 release
• f13827b Release Ember Data v2.10.0-beta.3
• 9ad22ce Update changelog for the Ember Data 2.10.0-beta.3 release
• 7231263 [PERF] fix sub-optimal compiler output (#4655) (#4656)
• f3df538 Release Ember Data 2.10.0-beta.2
• c6aefe7 Update Changelog for the Ember Data 2.10.0-beta.2 release
• 31480e1 [DOC] Add documentation for query#update() to refresh query
• 2b56fdf Release 2.10.0-beta.1
• 7a4beb0 Update changelog for the 2.10.0-beta.1 release
• 6d8e81b Update changelog for Ember Data 2.10.0-beta.1
• 9593e17 Merge pull request #4578 from runspired/fix/null-id-assertions
• 2d464dc fix assertion tests
• 58baca4 fix id in error message
• 97daea8 improved error messaging

There are 65 commits in total. See the full diff.

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

---

Your Greenkeeper Bot 🌴

[greenkeeper]

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