An in-range update of vscode is breaking the build 🚨

[greenkeeper[bot]]

The devDependency vscode was updated from 1.1.29 to 1.1.30.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

vscode is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

- ❌ **continuous-integration/travis-ci/push:** The Travis CI build failed ([Details](https://travis-ci.org/vstirbu/vscode-mermaid-preview/builds/496418063?utm_source=github_status&utm_medium=notification)).

---

Commits

The new version differs by 2 commits.

• e81d78a bump@1.1.30
• 4f6e30d Support passing user-data-dir to tests (#144)

See the full diff

FAQ and help

There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those don’t help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).

---

Your Greenkeeper Bot :palm_tree:

[greenkeeper[bot]]

After pinning to 1.1.29 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.

[greenkeeper[bot]]

• The devDependency vscode was updated from 1.1.30 to 1.1.31.

Your tests are still failing with this version. Compare changes

[greenkeeper[bot]]

• The devDependency vscode was updated from 1.1.31 to 1.1.32.

Your tests are still failing with this version. Compare changes

[greenkeeper[bot]]

• The devDependency vscode was updated from 1.1.32 to 1.1.33.

Your tests are still failing with this version. Compare changes