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

re-apply blueprint #27

Closed

Conversation

NullVoxPopuli
Copy link
Contributor

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"?

"release-it": "^12.2.1",
"release-it-lerna-changelog": "^1.0.3"
},
"engines": {
"node": "6.* || 8.* || >= 10.*"
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

breaking change

package.json Outdated Show resolved Hide resolved
@NullVoxPopuli
Copy link
Contributor Author

NullVoxPopuli commented Oct 18, 2020

looks like the modifier manager polyfill broke somehow?
all tests pass except for ember-source @ 2.18 and 3.4 (pre modifier-manager)

- "6"
- "10"
Copy link
Member

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...

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

can do!

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

#28

@RobbieTheWagner RobbieTheWagner added the duplicate This issue or pull request already exists label Oct 1, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
duplicate This issue or pull request already exists
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants