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

feat: upgrade to ember 3.28 #153

Merged
merged 1 commit into from
Oct 12, 2021
Merged

feat: upgrade to ember 3.28 #153

merged 1 commit into from
Oct 12, 2021

Conversation

GreatWizard
Copy link
Member

@GreatWizard GreatWizard commented Oct 7, 2021

Build

Upgrade to ember v3.28 (#153)

This PR must be considered as breaking:

  • Need ember-cli and ember-source as v3.20+

@GreatWizard GreatWizard force-pushed the feat/upgrade-3-28 branch 3 times, most recently from b1e0a9b to 673e495 Compare October 8, 2021 09:00
Comment on lines +35 to +49
name: 'ember-beta',
npm: {
devDependencies: {
'ember-source': await getChannelURL('beta'),
},
},
},
{
name: 'ember-canary',
npm: {
devDependencies: {
'ember-source': await getChannelURL('canary'),
},
},
},
Copy link
Member

@MrChocolatine MrChocolatine Oct 11, 2021

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.

Copy link
Member Author

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

Copy link
Member

@MrChocolatine MrChocolatine Oct 11, 2021

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.

@MrChocolatine
Copy link
Member

We already dropped the support for Node.js v10 in #139, so you can remove the line

Drop node 10 support

from the description of your PR.

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.

3 participants