An in-range update of mocha is breaking the build π¨
Closed this issue Β· 3 comments
Version 3.5.1 of mocha just got published.
Branch | Build failing π¨ |
---|---|
Dependency | mocha |
Current Version | 3.5.0 |
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
v3.5.13.5.1 / 2017-09-09
π° News
- π£ Mocha is now sponsoring PDXNode! If you're in the Portland area, come check out the monthly talks and hack nights!
π Fixes
- #2997: Fix missing
xit
export for "require" interface (@solodynamo) - #2957: Fix unicode character handling in XUnit reporter failures (@jkrems)
π© Other
- #2986: Add issue and PR templates (@kungapal)
- #2918: Drop bash dependency for glob-related tests (@ScottFreeCode)
- #2922: Improve
--compilers
coverage (@ScottFreeCode) - #2981: Fix tpyos and spelling errors (@jsoref)
Commits
The new version differs by 14 commits.
4070a44
Release v3.5.1
466ba73
update CHANGELOG.md for v3.5.1 [ci skip]
1cc0fc0
import/require xit, fixes #2972
74fa66f
update nyc to latest; remove workaround in travis script
aa52933
update coveralls strategy; closes #2984
73a5338
Spelling (#2981)
9f403bf
Add
utils.escape
tests and fix unicode escaping800acbc
whitelist "developer-experience" tag for stalebot [ci skip]
5895671
Added issue, pull request templates. (#2869)
075bd51
Merge pull request #2918 from mochajs/no-shell-test
8710438
Work around Node 0.10 Windows flake when testing
13b8340
Ensure that compiler lookup works and not just that transpilation works (#2922)
26d337a
Add tests for double-star behavior
c0e6b68
Eliminate glob.sh
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.5.0 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.
Version 3.5.2 just got published.
Your tests are still failing with this version. Compare the changes π¨
Release Notes
v3.5.23.5.2 / 2017-09-10
π Fixes
- #3001: Fix AMD-related failures first appearing in v3.5.1 (@boneskull)
Commits
The new version differs by 5 commits.
72622ab
Release v3.5.2
ac4c39f
fix version in CHANGELOG.md [ci skip]
f06d969
update CHANGELOG for 3.5.2 [ci skip]
9a3ddeb
fix AMD bundle by hacking around check in
he
module; closes #3000337d317
fix broken links in CHANGELOG.md [ci skip]
See the full diff
Version 3.5.3 just got published.
Your tests are still failing with this version. Compare the changes π¨