An in-range update of mocha is breaking the build π¨
Closed this issue Β· 1 comments
Version 3.2.0 of mocha just got published.
Branch | Build failing π¨ |
---|---|
Dependency | mocha |
Current Version | 3.1.2 |
Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
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 πͺ
Status Details
- β continuous-integration/travis-ci/push The Travis CI build failed Details
Release Notes
testing-coma3.2.0 / 2016-11-24
π° News
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.
π Bug Fix
-
#2535: Fix crash when
--watch
encounters broken symlinks (@villesau) -
#2593: Fix (old) regression; incorrect symbol shown in
list
reporter (@Aldaviva) - #2584: Fix potential error when running XUnit reporter (@vobujs)
π Enhancement
- #2294: Improve timeout error messaging (@jeversmann, @boneskull)
-
#2520: Add info about
--inspect
flag to CLI help (@ughitsaaron)
π© Other
- #2570: Use karma-mocha proper (@boneskull)
- Licenses updated to reflect new copyright, add link to license and browser matrix to
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.
Commits
The new version differs by 21 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 21 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 π΄
After pinning to 3.1.2 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.