This version is covered by your current version range and after updating it in your project the build went from success to failure.
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 :muscle:
Of course this could just be a false positive, caused by a flaky test suite, or third parties that are currently broken or unavailable, but that would be another problem I’d recommend working on.
Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right?
Are you unsure about how things are supposed to work?
There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.
Good luck with your project :sparkles:
You rock!
:palm_tree:
The new version differs by 256 commits (ahead by 256, behind by 11).
With Integrationsfirst-class bot support landed on GitHub and we’ve rewritten Greenkeeper to take full advantage of it. Simpler setup, fewer pull-requests, faster than ever.
Screencast Try it today. Free for private repositories during beta.
Coverage remained the same at 97.802% when pulling d248b62c1fbe2686b869be774849c324c38e1bdb on greenkeeper-ember-data-2.12.1 into 5806a5bacd67d5f7f33c0c53d9ef0db4cf525680 on master.
Hello lovely humans,
ember-data just published its new version 2.12.1.
This version is covered by your current version range and after updating it in your project the build went from success to failure.
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 :muscle:
Of course this could just be a false positive, caused by a flaky test suite, or third parties that are currently broken or unavailable, but that would be another problem I’d recommend working on.
Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right? Are you unsure about how things are supposed to work?
There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.
Good luck with your project :sparkles:
You rock!
:palm_tree:
The new version differs by 256 commits (ahead by 256, behind by 11).
83ff5f6
Release Ember Data 2.12.1
71978ee
Update changelog for the Ember Data 2.12.1 release
d101ed3
Merge pull request #4875 from runspired/fix/iife-release
d2fa315
Merge pull request #4881 from bmac/fix-release
1d959d9
Fix injection-test on the release branch
16c3014
ensure context is applied
868c90b
[BUGFIX] ensure the globals build has the correct context in the iife.
1d34bf0
Fix tests in release branch RE: factoryFor. (#4878)
fd06e1f
Pull in loader.js from the dist directory instead of the lib directory (#4824)
0f73468
Release Ember Data 2.12.0
6395eb7
Update the changelog for the Ember Data 2.12.0 release
04cbbb5
Release Ember Data 2.12.0-beta.4
8511886
Update changelog for the 2.12.0-beta.4 release
3637db8
[Fixes #4807] realize class + factory seperation
d7fbbad
Don’t redefine findPossibleInverses for each _findInverseFor
There are 250 commits in total. See the full diff.
Screencast
Try it today. Free for private repositories during beta.