-
Notifications
You must be signed in to change notification settings - Fork 142
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
Updates for LTS 3.28 including ember-data #1085
Conversation
Adding an Ember 3.28 LTS to the test matrix. We used to test is as "release" but now that has moved on. And in order to keep the suite the same size, I'm dropping the scenario for 3.20. We still test 3.16, our oldest supported LTS, which should give us plenty of coverage. Things that work in 3.16 and 3.24 are very unlikey to be broken in 3.20.
Co-authored-by: Sam Van Campenhout <sam.van.campenhout@gmail.com>
@@ -30,25 +30,25 @@ | |||
"broccoli-persistent-filter": "^3.1.2", | |||
"ember-bootstrap": "^4.6.3", | |||
"ember-cli-3.16": "npm:ember-cli@~3.16.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.
I'm curious, why keep 3.16 and drop 3.20?
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.
Purely to keep the test suite smaller. We still support both, we're just testing the older one of the two and assuming it's unlikely that the newer one is broken if LTS releases on either side of it are working.
This closes #1112 by removing our OneShot optimization hack in favor of turning on broccoli memoization by default. Broccoli memoization should absolutely be broccoli's default. It's not yet, but we can turn the flag on here unless users have explicitly turned it off.
Merged #1115 into here because I suspect it will unblock the failing tests here. |
Adding an Ember 3.28 LTS to the test matrix. We used to test is as "release" but now that has moved on.
And in order to keep the suite the same size, I'm dropping the scenario for 3.20. We still test 3.16, our oldest supported LTS, which should give us plenty of coverage. Things that work in 3.16 and 3.24 are very unlikey to be broken in 3.20.