greenkeeper[bot]
commented
7 years ago 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.3.0 of mocha just got published.
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 :muscle:
Status Details
- ❌ **continuous-integration/travis-ci/push** The Travis CI build failed [Details](https://travis-ci.org/GoogleChrome/npm-publish-scripts/builds/225143410)Release Notes
coveraveThanks to all our contributors, maintainers, sponsors, and users!❤️
As highlights:
--inspect-brkon command-line (@igwejk)semistandarddirectly (@kt3k)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 symbolThere are 89 commits in total.
See the full diff
Not sure how things should work exactly?
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html) and of course you may always [ask my humans](https://github.com/greenkeeperio/greenkeeper/issues/new).Your Greenkeeper Bot :palm_tree: