-
Notifications
You must be signed in to change notification settings - Fork 62
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update mocha to the latest version 🚀 #143
Conversation
Version 4.0.1 just got published.Update to this version instead 🚀 Release Notesv4.0.14.0.1 / 2017-10-05🐛 Fixes
CommitsThe new version differs by 6 commits.
See the full diff |
Version 4.1.0 just got published.Update to this version instead 🚀 Release Notesv4.1.04.1.0 / 2017-12-28This is mainly a "housekeeping" release. Welcome @Bamieh and @xxczaki to the team! 🐛: Fixes
🎉 Enhancements
📖 Documentation
🔩 Other
CommitsThe new version differs by 409 commits.
There are 250 commits in total. See the full diff |
Version 5.0.0 just got published.Update to this version instead 🚀 Release Notesv5.0.05.0.0 / 2018-01-17Mocha starts off 2018 right by again dropping support for unmaintained rubbish. Welcome @vkarpov15 to the team! 💥 Breaking Changes
🎉 Enhancements
🐛 Fixes
😎 Developer Experience📖 Documentation
🔩 Other
CommitsThe new version differs by 26 commits.
There are 26 commits in total. See the full diff |
Version 5.0.1 just got published.Update to this version instead 🚀 CommitsThe new version differs by 15 commits.
See the full diff |
Version 4.0.0 of mocha just got published.
The version 4.0.0 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.
Release Notes
v4.0.04.0.0 / 2017-10-02
You might want to read this before filing a new bug! 😝
💥 Breaking Changes
For more info, please read this article.
Compatibility
Default Behavior
node
from exiting will do so when run in Mocha. Supply the--exit
flag to revert to pre-v4.0.0 behavior (@ScottFreeCode, @boneskull)Reporter Output
stdout:
prefix from browser reporter logs (@skeggse)--forbid-pending
or--forbid-only
is specified (@ScottFreeCode)👎 Deprecations
--compilers
command-line option is now soft-deprecated and will emit a warning onSTDERR
. Read this for more info and workarounds (@ScottFreeCode, @boneskull)🎉 Enhancements
📖 Documentation
README.md
andCONTRIBUTING.md
(@skeggse)🔩 Other
Commits
The new version differs by 48 commits.
d69bf14
Release v4.0.0
171b9f9
pfix "prepublishOnly" potential portability problem
60e39d9
Update link to wiki (GitHub at the leading
--
)804f9d5
Update link because GitHub ate the leading
--
3326c23
update CHANGELOG for v4.0.0 [ci skip]
6dd9252
add link to wiki on --compilers deprecation
96318e1
Deprecate --compilers
92beda9
drop bower support
58a4c6a
remove unused .npmignore
7af6611
kill Date#toISOString shim
43501a2
reduce noise about slow tests; make a few tests faster, etc.
fa228e9
update --exit / --no-exit integration test for new default behavior
3fdd3ff
Switch default from forced exit to no-exit
c5d69e0
add integration tests for --exit/--no-exit
3a7f8dc
enhance runMochaJSON() helper by returning the subprocess instance
There are 48 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 🌴