Update mocha to version 3.2.0 🚀 #14
Open
Conversation
This file contains 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Hello lovely humans,
mocha just published its new version 3.2.0.
This version is not covered by your current version range.
Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.
I recommend you look into these changes and try to get onto the latest version of mocha.
Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.
Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right?
Are you unsure about how things are supposed to work?
There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.
Good luck with your project ✨
You rock!
🌴
GitHub Release
3.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
--watchencounters broken symlinks (@villesau)listreporter (@Aldaviva)🎉 Enhancement
--inspectflag to CLI help (@ughitsaaron)🔩 Other
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.
The new version differs by 193 commits .
b51e360Release v3.2.05badf0brebuild mocha.js for release v3.2.0 [ci skip]b1d6b49updateCHANGELOG.mdfor v3.2.0 [ci skip]7a05a6cuse spec reporter in tests by default; closes #2594004389ftweak timeout messaging; see #229412afaf7cleanup .gitignore [ci skip]edde033fix XUnit reporter output. Closes #2584f5bef7cRevert test pass symbol in List reporter4a2e85aignore files files which are not found by files() (#2538)79d7414Add Browser Support Matrix to README.md (#2590) [ci skip]1d52fd3use karma-mocha; closes #25708941442adds info about --inspect flag to options in --help71e7a1erename some fixture files that had the wrong extension1a45929typo in commentb5a424aLink license from current branchThere are 193 commits in total. See the full diff.
This pull request was created by greenkeeper.io.
Tired of seeing this sponsor message? ⚡
greenkeeper upgrade