An in-range update of mocha is breaking the build π¨
Closed this issue Β· 3 comments
Version 3.3.0 of mocha just got published.
| Branch | Build failing π¨ |
|---|---|
| Dependency | mocha |
| Current Version | 3.2.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](https://travis-ci.org/regexhq/dotfile-regex/builds/225194044)Release Notes
coveraveThanks to all our contributors, maintainers, sponsors, and users! β€οΈ
As highlights:
- We've got coverage now!
- Testing is looking less flaky \o/.
- No more nitpicking about "mocha.js" build on PRs.
π Enhancements
- #2659: Adds support for loading reporter from an absolute or relative path (@sul4bh)
- #2769: Support
--inspect-brkon command-line (@igwejk)
π Fixes
π Coverage
- #2672: Add coverage for node tests (@c089, @Munter)
- #2680: Increase tests coverage for base reporter (@epallerols)
- #2690: Increase tests coverage for doc reporter (@craigtaub)
- #2701: Increase tests coverage for landing, min, tap and list reporters (@craigtaub)
- #2691: Increase tests coverage for spec + dot reporters (@craigtaub)
- #2698: Increase tests coverage for xunit reporter (@craigtaub)
- #2699: Increase tests coverage for json-stream, markdown and progress reporters (@craigtaub)
- #2703: Cover .some() function in utils.js with tests (@seppevs)
- #2773: Add tests for loading reporters w/ relative/absolute paths (@sul4bh)
π© Other
- Remove bin/.eslintrc; ensure execs are linted (@boneskull)
- #2542: Expand CONTRIBUTING.md (@boneskull)
- #2660: Double timeouts on integration tests (@Munter)
- #2653: Update copyright year ([@Scottkao85], @Munter)
- #2621: Update dependencies to enable Greenkeeper (@boneskull, @greenkeeper)
- #2625: Use trusty container in travis-ci; use "artifacts" addon (@boneskull)
- #2670: doc(CONTRIBUTING): fix link to org members (@coderbyheart)
- Add Mocha propaganda to README.md (@boneskull)
- #2470: Avoid test flake in "delay" test (@boneskull)
- #2675: Limit browser concurrency on sauce (@boneskull)
- #2669: Use temporary test-only build of mocha.js for browsers tests (@Munter)
- Fix "projects" link in README.md (@boneskull)
- #2678: Chore(Saucelabs): test on IE9, IE10 and IE11 (@coderbyheart)
- #2648: Use
semistandarddirectly (@kt3k) - #2727: Make the build reproducible (@lamby)
Commits
The new version differs by 89 commits0.
fb1687e:ship: Release v3.3.01943e02Add Changelog for v3.3.0861e968Refactor literal play-icon hex code to a var1d3c5bcFix typo in karma.conf.js9bd9389Fix spec paths in test HTML files0a93024Adds tests for loading reporters w/ relative/absolute paths (#2773)73929adComment special treatment of '+' in URL query parsinge2c9514Merge pull request #2769 from igwejk/support_inspect_break_in_opts038c636Support--inspect-brkon command-lineb4ebabdMerge pull request #2727 from lamby/reproducible-build882347bPlease make the build reproducible.a2fc76cMerge pull request #2703 from seppevs/cover_utils_some_fn_with_testsed61cd0cover .some() function in utils.js with testsf42cbf4Merge pull request #2701 from craigtaub/landingSpec6065242use stubbed symbol
There are 89 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 π΄
Version 3.4.0 just got published.
Your tests are still failing with this version. Compare the changes π¨
Release Notes
v3.4.0Mocha is now moving to a quicker release schedule: when non-breaking changes are merged, a release should happen that week.
This week's highlights:
allowUncaughtadded to commandline as--allow-uncaught(and bugfixed)- warning-related Node flags
π Enhancements
- #2793, #2697: add --allowUncaught to Node.js (@lrowe)
- #2733: Add
--no-warningsand--trace-warningsflags (@sonicdoe)
π Fixes
π© Other
- #2778: Add license report and scan status (@xizhao)
- #2794: no special case for macOS running Karma locally (@boneskull)
- #2795: reverts use of semistandard directly ([#2648]) (@boneskull)
Commits
The new version differs by 9 commits0.
7554b31Add Changelog for v3.4.09f7f7edAdd--trace-warningsflag92561c8Add--no-warningsflagceee976lint test/integration/fixtures/simple-reporter.jsdcfc094Revert "usesemistandarddirectly"93392ddno special case for macOS running Karma locally4d1d91d--allow-uncaught cli optionfb1e083fix allowUncaught in browser4ed3fc5Add license report and scan status
false
See the full diff
Version 3.4.1 just got published.
Your tests are still failing with this version. Compare the changes π¨
Release Notes
Ohai CRLF...Fixed a publishing mishap with git's autocrlf settings.
Version 3.4.2 just got published.
Your tests are still failing with this version. Compare the changes π¨
Release Notes
fake-success3.4.2 / 2017-05-24
π Fixes
- #2802: Remove call to deprecated os.tmpDir (@makepanic)
- #2820: Eagerly set process.exitCode (@chrisleck)
π© Other
Commits
The new version differs by 7 commits.
a15b20a:ship: Release v3.4.2fc802a9:memo: Add Changelog for v3.4.210ff0ecEagerly set process.exitCode (#2820)fc35691Merge pull request #2818 from makepanic/issue/28023e7152fRemove call to deprecated os.tmpDir (#2802)e249434Merge pull request #2807 from mochajs/npm-script-lint17a1770Move linting into an npm script. Relates to #2805
See the full diff