-
-
Notifications
You must be signed in to change notification settings - Fork 33
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
[breaking] Update to Ember CLI 5.12.0 #81
Conversation
Using ember-cli-update to update dependencies and blueprints to the latest LTS CLI release.
Small changes in the prettier config in the default bluerpint. Applied here.
This is no longer recommended and is a linting violation. Removed them.
As this is the entire point of this code
@chriskrycho - first step to unlock #80 |
Seems reasonable; I think that makes this Breaking, right? |
Yup, I think so. I put that in the PR title, but can't l label. |
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.
👍🏼 Excellent! I’ll add the label and merge it!
"ember-source": "^3.8 || >= 4.0.0", | ||
"@glint/template": "^1.0.2" | ||
"@glint/template": "^1.0.2", | ||
"ember-source": ">= 4.0.0" |
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.
This adds support for Ember v6. Would be great if we could release it.
If you don't want to do another major yet, we could backport that small change of the supported ember-source
peer dependency. But it would be great if we could make this addon compatible with Ember v6.
Updated using ember-cli-update do update all blueprints and dependencies.
This is breaking:
Technically this just drops tests for these older things. I left in the
macroCondition(dependencySatisfies('ember-source'
for earlier ember versions as I don't think these have to go away today.The linting config has changes that I applied as well.