This version is covered by your current version range and after updating it in your project the build went from success to failure.
As mocha 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.
Under the foundation, all contributors to Mocha must sign the JS Foundation CLA before their code can be merged. When sending a PR--if you have not already signed the CLA--a friendly bot will ask you to do so.
Coverage remained the same at 100.0% when pulling 37c1a9a78ceda42730b28d42506a8aeb63bede33 on greenkeeper-mocha-3.2.0 into 2de6d2649a4ba4e712193de8412fca43b94d309e on master.
Hello lovely humans,
mocha just published its new version 3.2.0.
This version is covered by your current version range and after updating it in your project the build went from success to failure.
As mocha 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:
GitHub Release
3.2.0 / 2016-11-24
Mocha is now a JS Foundation Project!
Mocha is proud to have joined the JS Foundation. For more information, read the announcement.
Contributor License Agreement
Under the foundation, all contributors to Mocha must sign the JS Foundation CLA before their code can be merged. When sending a PR--if you have not already signed the CLA--a friendly bot will ask you to do so.
Mocha remains licensed under the MIT license.
--watch
encounters broken symlinks (@villesau)list
reporter (@Aldaviva)--inspect
flag to CLI help (@ughitsaaron)README.md
(@boneskull, @ScottFreeCode, @dasilvacontin)Thanks to all our contributors, sponsors and backers! Keep on the lookout for a public roadmap and new contribution guide coming soon.
The new version differs by 72 commits .
b51e360
Release v3.2.0
5badf0b
rebuild mocha.js for release v3.2.0 [ci skip]
b1d6b49
update
CHANGELOG.md
for v3.2.0 [ci skip]7a05a6c
use spec reporter in tests by default; closes #2594
004389f
tweak timeout messaging; see #2294
12afaf7
cleanup .gitignore [ci skip]
edde033
fix XUnit reporter output. Closes #2584
f5bef7c
Revert test pass symbol in List reporter
4a2e85a
ignore files files which are not found by files() (#2538)
79d7414
Add Browser Support Matrix to README.md (#2590) [ci skip]
1d52fd3
use karma-mocha; closes #2570
8941442
adds info about --inspect flag to options in --help
71e7a1e
rename some fixture files that had the wrong extension
1a45929
typo in comment
b5a424a
Link license from current branch
There are 72 commits in total. See the full diff.
This pull request was created by greenkeeper.io.
Tired of seeing this sponsor message? :zap:
greenkeeper upgrade