An in-range update of ember-cli-qunit is breaking the build 🚨 #143
Comments
After pinning to 4.0.1 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results. |
Version 4.1.0 just got published.Your tests are still failing with this version. Compare the changes 🚨 CommitsThe new version differs by 20 commits ahead by 20, behind by 2.
There are 20 commits in total. See the full diff |
Version 4.1.1 just got published.Your tests are still failing with this version. Compare the changes 🚨 |
Version 4.2.0 just got published.Your tests are still failing with this version. Compare the changes 🚨 |
Version 4.2.1 just got published.Your tests are still failing with this version. Compare the changes 🚨 CommitsThe new version differs by 6 commits.
See the full diff |
Version 4.3.0 just got published.Your tests are still failing with this version. Compare the changes 🚨 |
Version 4.3.1 just got published.Your tests are still failing with this version. Compare the changes 🚨 |
Version 4.3.2 just got published.Your tests are still failing with this version. Compare the changes 🚨 |
Version 4.0.2 of ember-cli-qunit was just published.
This version is covered by your current version range and after updating it in your project the build failed.
ember-cli-qunit is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.
Status Details
Commits
The new version differs by 2 commits.
f1e2859
v4.0.2
70457c5
Migrate from qunitjs to qunit.
See the full diff
FAQ and help
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot 🌴
The text was updated successfully, but these errors were encountered: