Upgrade ember-qunit to address canary deprecations #911
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Based off #903, but avoiding latest conflicts with master and handling the breaking changes in all packages.
|
FYI: I'm currently working to address some issues related to this specifically emberjs/ember-string#259 which is a "leaf" activity, preventing us from properly upgrading due to ember canary removals of some modules... Many of the issues have been fixed now, but I'm trying to tie up some loose ends. Feel free to ping me to sync up, so we don't step on each others toes |
This was referenced Jul 29, 2021
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Based off #903, but avoiding latest conflicts with master and handling the breaking changes in all packages.