Closed elwayman02 closed 1 year ago
Actually, I believe ember-qunit and some other dependencies are finally forcing a drop of support for <3.28. I'll go ahead and remove these scenarios as it was going to be a major version bump anyway, and it's probably about time to drop support for Ember versions that have long been EOL'd. If you feel strongly that those scenarios need to be maintained still, I'm open to you pushing the proper changes to this branch to keep them working. 👍
We can probably drop node 10/12 support as well as part of this major release. What do you think?
We can probably drop node 10/12 support as well as part of this major release. What do you think?
@elwayman02 we should do it in a separate PR, right?
Yea, it doesn't have to be done in this PR as long as the CI builds pass once someone enables them.
On Mon, Mar 27, 2023 at 7:37 AM Sergey Astapov @.***> wrote:
We can probably drop node 10/12 support as well as part of this major release. What do you think?
@elwayman02 https://github.com/elwayman02 we should do it in a separate PR, right?
— Reply to this email directly, view it on GitHub https://github.com/machty/ember-concurrency/pull/515#issuecomment-1485232457, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAKDTKU3S5NSM4WUWWF4LDTW6GQZDANCNFSM6AAAAAAWEQGQCE . You are receiving this because you were mentioned.Message ID: @.***>
@machty are you able to take a look at this? It would be great to get tests actively running against an explicit 4.x LTS scenario soon. :)