-
Notifications
You must be signed in to change notification settings - Fork 43
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ship 2.0 #109
Comments
Probably a good opportunity to drop Node 10 as well? |
I would like to support old versions of Ember, as the point of this library is to help complex/large apps upgrade and there are many not on 3.16. However I have no problem requiring Ember CLI 3.16+ and something newer than Node 10. The addon isn't helping upgrade those things, apps can upgrade them independently of Ember and should. |
Yeah I think that’s consistent with the support policies. Since node 10 is EOL, if we don’t drop it now we are going to have issues when other deps start dropping node 10, especially when not all of them bump major when doing so. |
Ya, let’s make node engines |
This can be closed, yes? |
🎉 Yep! |
This issue tracks work blocking the release of a final 2.0 release.
ember-cli-deprecation-workflow 2.0 will introduce the following breaking changes:
TODO:
See also https://github.com/mixonic/ember-cli-deprecation-workflow/labels/2.0
The text was updated successfully, but these errors were encountered: