This version 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.
Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right?
Are you unsure about how things are supposed to work?
There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.
Good luck with your project :sparkles:
You rock!
:palm_tree:
The new version differs by 199 commits (ahead by 199, behind by 1).
With Integrationsfirst-class bot support landed on GitHub and we’ve rewritten Greenkeeper to take full advantage of it. Simpler setup, fewer pull-requests, faster than ever.
Screencast Try it today. Free for private repositories during beta.
Hello lovely humans,
qunitjs just published its new version 2.3.1.
This version 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.
Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right? Are you unsure about how things are supposed to work?
There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.
Good luck with your project :sparkles:
You rock!
:palm_tree:
The new version differs by 199 commits (ahead by 199, behind by 1).
5d675102.3.161ae877Build: Prepare 2.3.1 release, including authors and history updatedbf200fTests: EmitsuiteEndand triggermoduleDonefor parent modules63bcd15Docs: Remove trailing slash from some urlsbddf858All: Enable ESLint indent rule (#1143)1d5df85Docs: Update assert.async documentationa2c4567Assert: Allow assertions after asyncfcd93e0Docs: Copy styles from jquery-wp-content0414ddeDocs: Render markdown inside HTML blocks878d7baCore: Ensure assertions occur while test is running1854482Assert: Throw if async callback invoked after test finishes0179f47Tests: Add additional events test76c6dd3Tests: Re-order events teste586edaCore: Slim assertions after reporting them004ca6bCore: Fix test instance memory leak (#1138)There are 199 commits in total. See the full diff.
Screencast
Try it today. Free for private repositories during beta.