Ember Addons - Deprecations and backwards compatibility


#1

I’m looking for some advice on addon releases and ember versions.

Addons that use deprecated apis will raise a warning in the parent app and new syntax may fail entirely. When I publish an addon I want to keep step with the latest ember release but I don’t want to break consuming apps after addon updates.

What is the recommended way of avoiding this? NPM version pinning + compatibility notes in the README?


#2

One practice I’ve seen, but haven’t tried myself, is version your addons in lock step with Ember.