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

Updates for LTS 3.28 including ember-data #1085

Merged
merged 10 commits into from
Feb 8, 2022
Merged

Updates for LTS 3.28 including ember-data #1085

merged 10 commits into from
Feb 8, 2022

Conversation

ef4
Copy link
Contributor

@ef4 ef4 commented Jan 23, 2022

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.

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 <[email protected]>
@@ -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",
Copy link
Collaborator

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?

Copy link
Contributor Author

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.
@ef4
Copy link
Contributor Author

ef4 commented Feb 8, 2022

Merged #1115 into here because I suspect it will unblock the failing tests here.

@ef4 ef4 merged commit 4611fd1 into main Feb 8, 2022
@ef4 ef4 deleted the adjust-lts-scenarios branch February 8, 2022 05:54
@ef4 ef4 changed the title Adjust lts scenarios Updates for LTS 3.28 including ember-data Feb 8, 2022
@ef4 ef4 added the enhancement New feature or request label Feb 8, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants