Skip to content
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

Closed
wants to merge 8 commits into from
Closed

Fix CI builds #664

wants to merge 8 commits into from

Conversation

Turbo87
Copy link
Contributor

@Turbo87 Turbo87 commented Sep 26, 2019

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

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
@Turbo87 Turbo87 changed the title CI: Run Ember 3.13+ tests on Node.js 8 Fix CI builds Sep 26, 2019
@Turbo87
Copy link
Contributor Author

Turbo87 commented Sep 26, 2019

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
@Turbo87
Copy link
Contributor Author

Turbo87 commented Sep 26, 2019

It looks like the only things that are now legitimately failing CI are the changes in Ember 3.13 like:

Assertion Failed: EmberObject.create no longer supports defining computed properties. Define computed properties using extend() or reopen() before calling create().

Those are addressed by #662 AFAIK

@Turbo87 Turbo87 closed this Oct 28, 2019
@Turbo87
Copy link
Contributor Author

Turbo87 commented Oct 28, 2019

closed in favor of #667

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant