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

[greenkeeper]

The devDependency vscode was updated from 1.1.30 to 1.1.31.

🚨 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

• ✅ codecov/project: No report found to compare against (Details).
• ❌ svn-scm: #20190320.3 failed (Details).

---

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]

• The devDependency vscode was updated from 1.1.31 to 1.1.32.

Your tests are still failing with this version. Compare changes

[greenkeeper]

After pinning to 1.1.30 your tests are passing again. Downgrade this dependency 📌.

[ilgatto88]

Dear Christopher,
since a few updates the svn extension for Visual Studio Code seems to be broken. At least I cannot commit the changes, however commiting in the terminal with svn commands is working without issues.
svn extension version: 1.47.5
vscode version: 1.32.3
Could you please have a look at the problem?
Thank you in advance.

[edgardmessias]

Please, open a issue or start a talk here: https://gitter.im/svn-scm/Lobby

[greenkeeper]

• The devDependency vscode was updated from 1.1.32 to 1.1.33.

Your tests are still failing with this version. Compare changes