-
Notifications
You must be signed in to change notification settings - Fork 3
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
feat: upgrade to ember 3.28 #153
Conversation
b1e0a9b
to
673e495
Compare
673e495
to
638956f
Compare
name: 'ember-beta', | ||
npm: { | ||
devDependencies: { | ||
'ember-source': await getChannelURL('beta'), | ||
}, | ||
}, | ||
}, | ||
{ | ||
name: 'ember-canary', | ||
npm: { | ||
devDependencies: { | ||
'ember-source': await getChannelURL('canary'), | ||
}, | ||
}, | ||
}, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we really to add back the scenarios beta
and canary
? (see #139)
I thought we wanted to get rid of these from all our Ember.js projects.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's not in the CI, juste configured in try
I don't see any reasons to not keep it here for the future ^^ as long as it's disabled on the CI
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah my bad, I went too fast and thought the CI would run again these 2 scenarios.
We already dropped the support for Node.js v10 in #139, so you can remove the line
from the description of your PR. |
Build
Upgrade to ember v3.28 (#153)
This PR must be considered as breaking: