Update ember and remove an outdated dep #277
Conversation
We recently upgraded ember-data, but not ember itself. This also removes an unneeded package; it was there for pre-2.0 reasons, but we've upgraded past 2.0.
|
(Greenkeeper can't see bower's stuff, that's why it didn't upgrade ember) |
|
Oh these should be updated in lockstep? Good to know! |
|
They don't have to be, but you know, it's easiest to stay abreast of changes if we keep up. :) |
|
they can be lockstep, but generally not required. Unless you use some new feature in ember-data that depends on a more recent version of ember. But that should be rare, especially if usage isn't changing but deps are merely being bumped. TL;DR general semver constraints should be upheld. |
|
@stefanpenner any comment about the warnings? |
|
emberjs/ember.js#13030 might be related |
|
Ahhhhhh yes that would make sense. On Tue, Mar 1, 2016 at 1:36 PM, Stefan Penner [email protected]
|
Update ember and remove an outdated dep
We recently upgraded ember-data, but not ember itself.
This also removes an unneeded package; it was there for pre-2.0
reasons, but we've upgraded past 2.0.
@wycats , this introduces warnings:
One for views as well. As far as I can tell, none of our code (nor our dependencies' code) uses the deprecated stuff; is this an unconditional warning?