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

Upgrade qunit to v2.7.1 #369

Merged
merged 1 commit into from
Oct 17, 2018
Merged

Upgrade qunit to v2.7.1 #369

merged 1 commit into from
Oct 17, 2018

Conversation

stefanpenner
Copy link
Member

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==
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@Turbo87 Turbo87 changed the title Upgrade qunit, disallowing old versions: Upgrade qunit to v2.7.1 Oct 17, 2018
@Turbo87 Turbo87 added the bug label Oct 17, 2018
@Turbo87 Turbo87 merged commit 986f9f8 into master Oct 17, 2018
@Turbo87 Turbo87 deleted the upgrade branch October 17, 2018 20:06
@stefanpenner
Copy link
Member Author

released as v3.5.2 🎉

@Turbo87
Copy link
Member

Turbo87 commented Oct 18, 2018

@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...

@rwjblue
Copy link
Member

rwjblue commented Oct 18, 2018

I guess we need to republish 3.5.1 as 3.5.3, and get 4.0.0 out with this change.

@stefanpenner
Copy link
Member Author

bah

@Turbo87
Copy link
Member

Turbo87 commented Oct 19, 2018

@stefanpenner I'm not sure how to interpret this comment

@Turbo87
Copy link
Member

Turbo87 commented Oct 19, 2018

I have re-released v3.5.1 as v3.5.3 and updated the changelog, the v4.0.0 release will follow later.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants