This repository was archived by the owner on Oct 2, 2021. It is now read-only.
Update mocha to the latest version 🚀 #648
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Contributor
|
🎉 This PR is included in version 4.2.2 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
☝️ Greenkeeper’s updated Terms of Service will come into effect on April 6th, 2018.
Version 5.1.0 of mocha was just published.
The version 5.1.0 is not covered by your current version range.
If you don’t accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.
It might be worth looking into these changes and trying to get this project onto the latest version of mocha.
If you have a solid test suite and good coverage, a passing build is a strong indicator that you can take advantage of these changes directly by merging the proposed change into your project. If the build fails or you don’t have such unconditional trust in your tests, this branch is a great starting point for you to work on the update.
Release Notes
v5.1.05.1.0 / 2018-04-12
🎉 Enhancements
--excludeoption (@metalex9)🐛 Fixes
📖 Documentation
🔩 Other
Commits
The new version differs by 23 commits ahead by 23, behind by 2.
40d9ea3Release v5.1.0bf34e42update CHANGELOG for v5.1.0 [ci skip]63462ddImplement API documentation using npm:documantation.741b0bdfix circular objects in json reporter; closes #2433 (#3318)8010501fix wrong version in package.json! [ci skip]94e7289doc precision for exclusive tests8b6c957optimize package-scripts.jsd71b80aPATH workaround for Travis CI bug7544bd3further build improvements (#3315)88b9882update package-lock.json for v5.0.5 [ci skip]4ae26b2improve caching performance in CI (#3310)ff9f3cfupdate stages and build matrices (#3308)f2560e7add update-contributors script; closes #3289 (#3290)cd1c835upgrade eslint; lint35dac3euse build stages for Travis CI (#3302)There are 23 commits in total.
See the full diff
FAQ and help
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper bot 🌴