-
Notifications
You must be signed in to change notification settings - Fork 6
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
Update qunitjs to the latest version 🚀 #215
base: master
Are you sure you want to change the base?
Conversation
Version 2.2.0 just got published.Update to this version instead 🚀 CommitsThe new version differs by 34 commits (ahead by 34, behind by 1).
There are 34 commits in total. See the full diff. |
Version 2.2.1 just got published.Update to this version instead 🚀 CommitsThe new version differs by 6 commits (ahead by 6, behind by 1).
See the full diff. |
Version 2.3.0 just got published.Update to this version instead 🚀 CommitsThe new version differs by 19 commits (ahead by 19, behind by 1).
There are 19 commits in total. See the full diff. |
Version 2.3.1 just got published.Update to this version instead 🚀 Release Notes2.3.1
CommitsThe new version differs by 19 commits (ahead by 19, behind by 1).
There are 19 commits in total. See the full diff. |
Version 2.3.3 just got published.Update to this version instead 🚀 Release Notes2.3.3
CommitsThe new version differs by 20 commits ahead by 20, behind by 1.
There are 20 commits in total. See the full diff |
Version 2.4.0 just got published.Update to this version instead 🚀 CommitsThe new version differs by 27 commits ahead by 27, behind by 1.
There are 27 commits in total. See the full diff |
Version 2.4.1 just got published.Update to this version instead 🚀 CommitsThe new version differs by 21 commits ahead by 21, behind by 1.
There are 21 commits in total. See the full diff |
Version 2.1.1 of qunitjs just got published.
The version 2.1.1 is not covered by your current version range.
Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.
I recommend you look into these changes and try to get onto the latest version of qunitjs.
Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.
Commits
The new version differs by 125 commits (ahead by 125, behind by 1).
677a0b5
2.1.1
9d34d13
Build: Prepare 2.1.1 release, including authors and history update
0c56b4e
Assert: Refactor to use ES6 where appropricate
e43fbc5
Assert: Refactor Assert to be ES6 class
bdd634d
All: Remove deprecated 1.x features
265c04f
Reporter: move urlparams import from reporter to html
5fd79d6
Assert: Deprecate assert.push
c65800b
Build: Remove unnecessary QUnit.load call
0e9c683
Core: QUnit.start does not require calliing QUnit.load
8edefa2
HTML Reporter: Add an abort button
365f8d2
Build: Run coverage during CI
294ba43
Build: Re-introduce code coverage for Browser tests
7dfe400
Build: Re-introduce code coverage for Node tests
a46fbb5
Build: Replace grunt-contrib-concat with grunt-contrib-copy
da70f9d
Build: Remove npm prepublish script
There are 125 commits in total. See the full diff.
Not sure how things should work exactly?
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot 🌴