-
-
Notifications
You must be signed in to change notification settings - Fork 174
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
Fix CI builds #664
Fix CI builds #664
Conversation
Ember 3.13 and above are no longer supporting Node.js 6, but since this project still supports it and dropping support would be a breaking change we need to adjust our CI pipeline to use Node.js 8 instead for the ember-try scenarios that need it.
... which still supports Node.js 6 see poetic/ember-cli-github-pages@aa46772#r34236099
... which still supports Node.js 6 see ef4/ember-code-snippet#60 (comment)
... which still supports Node.js 6 see sass/dart-sass@d0f471c#commitcomment-35247983
... which still supports Node.js 6
as suggested in their documentation
Originally this PR was only about using the correct Node.js version per Ember.js release but it turned out that a lot of other things were also broken. The PR now also pins a few dependencies to specific versions where Node.js 6 is still supported and it fixes a broken prettier check. Hopefully CI should be 🍏 now after all these changes. |
... which still supports Node.js 6 see socketio/engine.io#589
It looks like the only things that are now legitimately failing CI are the changes in Ember 3.13 like:
Those are addressed by #662 AFAIK |
closed in favor of #667 |
Ember 3.13 and above are no longer supporting Node.js 6, but since this project still supports it and dropping support would be a breaking change we need to adjust our CI pipeline to use Node.js 8 instead for the ember-try scenarios that need it.
(as suggested in #662 (comment))
/cc @GavinJoyce @rwjblue @offirgolan