This version is covered by your current version range and after updating it in your project the build went from success to failure.
As qunitjs is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.
I recommend you give this issue a high priority. I’m sure you can resolve this :muscle:
Of course this could just be a false positive, caused by a flaky test suite, or third parties that are currently broken or unavailable, but that would be another problem I’d recommend working on.
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 105 commits (ahead by 105, 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.2.1.
This version is covered by your current version range and after updating it in your project the build went from success to failure.
As qunitjs is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.
I recommend you give this issue a high priority. I’m sure you can resolve this :muscle:
Of course this could just be a false positive, caused by a flaky test suite, or third parties that are currently broken or unavailable, but that would be another problem I’d recommend working on.
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 105 commits (ahead by 105, behind by 1).
2aa54fa2.2.13e00b7aBuild: Prepare 2.2.1 release, including authors and history updatef40e35cTest: Add basic reorder test31d4ffaCore: Fix sessionStorage feature detection1e39704Tests: Ensure onError tests are included in test/index.html (#1111)2489111Build: Updating the master version to 2.2.1-pre.acab8ecBuild: Prepare 2.2.0 release, including authors and history update2cc7e05All: Enable some ES2015-specific ESLint rulesbaff17dCore: QUnit.onError now expects error or error-like objecte0b36a9Tests: Cleaning up window.onerror test HTML filesd5c2cd6HTML Reporter: Use QUnit.onError64821f8Tests: Adding tests for calling context in onerror tests029f199HTML Reporter: Ensure window.onerror return values are correct829c41fTests: Adding tests for QUnit.onError outside of QUnit tests4fc12b6HTML Reporter: Moving window.onerror to HTML ReporterThere are 105 commits in total. See the full diff.
Screencast
Try it today. Free for private repositories during beta.