This repository has been archived by the owner on Jan 3, 2024. It is now read-only.
[email protected] breaks build 🚨 #15
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 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.
Hello lovely humans,
mocha just published its new version 3.4.0.
This version is covered by your current version range and after updating it in your project the build went from success to failure.
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 💪
Of course this could just be a false positive, caused by a flaky test suite, or third parties that are currently broken or unavailable, but that would be another problem I’d recommend working on.
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
Mocha 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)🎉 Enhancements
--no-warningsand--trace-warningsflags (@sonicdoe)🐛 Fixes
🔩 Other
The new version differs by 170 commits .
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 statusfb1687e: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)There are 170 commits in total. See the full diff.