-
-
Notifications
You must be signed in to change notification settings - Fork 154
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
Upgrade qunit to v2.7.1 #369
Conversation
qunit@~2.7.1: | ||
version "2.7.1" | ||
resolved "https://registry.yarnpkg.com/qunit/-/qunit-2.7.1.tgz#ab93d322e46d8457d52fe4fa49d76da8cc476fec" | ||
integrity sha512-ePeNs/CVL8coOWxnjxQAp9mCvRJybEQw3rwJe1TUClL+WrIcaZkLeW7VxHWtshn0L0ZtY0y80JqC7+po7330Ng== |
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.
@Turbo87 ^^
released as v3.5.2 🎉 |
@stefanpenner this should have been v4.0.0 as it includes #354, which is a breaking change. please rerelease v3.5.1 as v3.5.3, and v3.5.2 as v4.0.0. also please make sure to update https://github.com/emberjs/ember-qunit/blob/master/CHANGELOG.md, which would have made the situation more visible. I think @rwjblue also wanted to make #348 part of v4.0.0, so maybe we shouldn't publish v4.0.0 just yet anyway... |
I guess we need to republish 3.5.1 as 3.5.3, and get 4.0.0 out with this change. |
bah |
@stefanpenner I'm not sure how to interpret this comment |
I have re-released v3.5.1 as v3.5.3 and updated the changelog, the v4.0.0 release will follow later. |
qunitjs/qunit#1319 (comment)