Skip to content
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

mocha@3.1.0 breaks build 🚨 #13

Merged
merged 1 commit into from
Sep 30, 2016
Merged

Conversation

greenkeeperio-bot
Copy link
Contributor

Hello lovely humans,

mocha just published its new version 3.1.0.

State Failing tests 🚨
Dependency mocha
New version 3.1.0
Type devDependency

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

3.1.0 / 2016-09-27

🎉 Enhancement

  • #2357: Support --inspect on command-line (@simov)
  • #2194: Human-friendly error if no files are matched on command-line (@Munter)
  • #1744: Human-friendly error if a Suite has no callback (BDD/TDD only) (@anton)

🐛 Bug Fix

  • #2488: Fix case in which variables beginning with lowercase "D" may not have been reported properly as global leaks (@JustATrick) 😆
  • #2465: Always halt execution in async function when this.skip() is called (@boneskull)
  • #2445: Exits with expected code 130 when SIGINT encountered; exit code can no longer rollover at 256 (@Munter)
  • #2315: Fix uncaught TypeError thrown from callback stack (@1999)
  • Fix broken only()/skip() in IE7/IE8 (@boneskull)
  • #2502: Fix broken stack trace filter on Node.js under Windows (@boneskull)
  • #2496: Fix diff output for objects instantiated with String constructor (more) (@boneskull)

The new version differs by 27 commits .

  • 9915dfb Release v3.1.0
  • 037cdae build dist for v3.1.0
  • 44a031b CHANGELOG for v3.1.0 [ci skip]
  • 8431cb3 fix diff output for String objects; closes #2496 (#2499)
  • 8bf1f29 ensure windows compat with stack trace filter; closes #2502 (#2503)
  • 8ccccba fix problems with only/skip in IE7/IE8
  • 8ef51a5 use HTML reporter and default to autoWatch/singleRun mode
  • 96e20df attempt windows-friendly reproducible case for #2315
  • f1ac548 fix: fix uncaught TypeError if error occurs on next tick, closes #2315 (#2439)
  • 3a2dae8 helpful error when necessary suite callback omitted; closes #1744
  • e22c407 Fix an issue and add relevant tests when describe and xdescribe fail when not supplied with a callback (issue #1744).
  • 9e7f5f2 Merge branch 'issue/2383'
  • 93e9fc9 rename more fixtures; closes #2383
  • 1786fe2 Report non-match to STDERR and exit if no files are matched (#2450)
  • 3e22a83 Exit process with correct error codes (#2445)

There are 27 commits in total. See the full diff.


This pull request was created by greenkeeper.io.

Tired of seeing this sponsor message? ⚡ greenkeeper upgrade

@JamesMessinger JamesMessinger merged commit af0f21c into master Sep 30, 2016
@JamesMessinger JamesMessinger deleted the greenkeeper-mocha-3.1.0 branch September 30, 2016 08:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants