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

[greenkeeper]

---

☝️ Important announcement: Greenkeeper will be saying goodbye 👋 and passing the torch to Snyk on June 3rd, 2020! Find out how to migrate to Snyk and more at greenkeeper.io

---

The devDependency vscode was updated from 1.1.36 to 1.1.37.

🚨 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 could not complete due to an error (Details).

---

Commits

The new version differs by 6 commits.

• c871436 v1.1.37
• e55dfe8 Clean up for new release
• faa0254 Merge pull request #170 from microsoft/pine/154
• 71ff0ef Fix #154
• 216c61a Merge pull request #169 from microsoft/dependabot/npm_and_yarn/https-proxy-agent-2.2.4
• e1e0c6c Bump https-proxy-agent from 2.2.1 to 2.2.4

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

[greenkeeper]

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