-
Notifications
You must be signed in to change notification settings - Fork 1
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
An in-range update of mocha is breaking the build 🚨 #7
Comments
Version 3.4.1 just got published.Your tests are still failing with this version. Compare the changes 🚨 Release NotesOhai 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 Notesfake-success3.4.2 / 2017-05-24🐛 Fixes
🔩 OtherCommitsThe new version differs by 7 commits.
See the full diff |
Version 3.5.0 just got published.Your tests are still failing with this version. Compare the changes 🚨 Release Notesfree-as-in-freezing3.5.0 / 2017-07-31📰 News
🔒 Security Fixes
🎉 Enhancements
🔩 Other
CommitsThe new version differs by 34 commits.
There are 34 commits in total. See the full diff |
Version 3.5.1 just got published.Your tests are still failing with this version. Compare the changes 🚨 Release Notesv3.5.13.5.1 / 2017-09-09📰 News
🐛 Fixes
🔩 Other
CommitsThe new version differs by 14 commits.
See the full diff |
Version 3.5.2 just got published.Your tests are still failing with this version. Compare the changes 🚨 Release Notesv3.5.23.5.2 / 2017-09-10🐛 Fixes
CommitsThe new version differs by 5 commits.
See the full diff |
Version 3.5.3 just got published.Your tests are still failing with this version. Compare the changes 🚨 Release Notesv3.5.33.5.3 / 2017-09-11🐛 Fixes |
Version 3.4.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 💪
Status Details
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:
allowUncaught
added to commandline as--allow-uncaught
(and bugfixed)🎉 Enhancements
--no-warnings
and--trace-warnings
flags (@sonicdoe)🐛 Fixes
🔩 Other
Commits
The new version differs by 9 commits0.
7554b31
Add Changelog for v3.4.0
9f7f7ed
Add
--trace-warnings
flag92561c8
Add
--no-warnings
flagceee976
lint test/integration/fixtures/simple-reporter.js
dcfc094
Revert "use
semistandard
directly"93392dd
no special case for macOS running Karma locally
4d1d91d
--allow-uncaught cli option
fb1e083
fix allowUncaught in browser
4ed3fc5
Add license report and scan status
false
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 🌴
The text was updated successfully, but these errors were encountered: