-
-
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
re-apply blueprint #27
Conversation
"release-it": "^12.2.1", | ||
"release-it-lerna-changelog": "^1.0.3" | ||
}, | ||
"engines": { | ||
"node": "6.* || 8.* || >= 10.*" |
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.
breaking change
- "6" | ||
- "10" |
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.
Can you do this (along with the package.json engines update) in a stand alone PR? Specifically to call out the breaking change of dropping old node support...
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.
can do!
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.
while working on #25,
I noticed that the linting didn't like decorators (wanted to use @Tracked for adding tests).
I figured the last blueprint applied to this addon was pre-octane, so re-applying ember-cli-update hopefully "just works"?