The devDependency semantic-release was updated from 15.13.20 to 15.13.21.

🚨 View failing branch.

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

semantic-release 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.

Your Greenkeeper Bot 🌴

🚨 Reminder! Less than one month left to migrate your repositories over to Snyk before Greenkeeper says goodbye on June 3rd! 💜 🚚💨 💚

Find out how to migrate to Snyk at greenkeeper.io

The devDependency vscode-test was updated from 1.3.0 to 1.4.0.

🚨 View failing branch.

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

vscode-test 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.

Your Greenkeeper Bot 🌴

Though the SVN integration of the main plugins works fine on my installation of VSC for MacOS (correctly configured with proper svn commands path), the svn-ext plugin fails at launch because of this:

[2020-10-09 13:00:13.854] [renderer1] [error] spawn svn.exe ENOENT: Error: spawn svn.exe ENOENT at Process.ChildProcess._handle.onexit (internal/child_process.js:264:19) at onErrorNT (internal/child_process.js:456:16) at processTicksAndRejections (internal/process/task_queues.js:81:21)

The devDependency @types/xml2js was updated from 0.4.4 to 0.4.5.

🚨 View failing branch.

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

@types/xml2js 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.

Your Greenkeeper Bot 🌴

The devDependency @types/node was updated from 11.12.2 to 11.12.3.

🚨 View failing branch.

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

@types/node 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.

Your Greenkeeper Bot 🌴

This error message is popping up every time I restart VSCode. I am using VS Code insider version. On Windows 10.

I installed the iconv-lite package as instructed in the message, but it is not changing this situation.

Let me know if you require any further details.

I tried to install svn-scm-ext ona vscode WSL connection and after installing iconv-lite tackage it requested, VSCode fails to open with a "Connection error: Unauthorized client refused." error.

Now I tried to uninstall svn-scm-ext it and got the same Connection error: Unauthorized client refused error.

It has screw up my vscode setup.

🚨 The automated release from the master branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can resolve this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the master branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here is some links that can help you:

• Usage documentation
• Frequently Asked Questions
• Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

No npm token specified.

An npm token must be created and set in the NPM_TOKEN environment variable on your CI environment.

Please make sure to create an npm token and to set it in the NPM_TOKEN environment variable on your CI environment. The token must allow to publish to the registry https://registry.npmjs.org/.

Good luck with your project ✨

Your semantic-release bot 📦🚀

Hi, I think that jschardet should now be moved to dependencies.

Is that possible to show all revision logs related to the file? Currently it seems that only latest five revisions(including HEAD) are displayed.

The devDependency mocha was updated from 6.2.1 to 6.2.2.

🚨 View failing branch.

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

mocha 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.

Your Greenkeeper Bot 🌴

The devDependency @types/semver was updated from 6.0.1 to 6.0.2.

🚨 View failing branch.

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

@types/semver 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.

Your Greenkeeper Bot 🌴

Select Open SVN History menu.
The history tab opens with error:

There was an error retrieving the hostory from Subversion:
--
svn: E200033: Another process is blocking the working copy database, or 
the underlying filesystem does not support file locking; if the working copy 
is on a network filesystem, make sure file locking has been enabled on the 
file server svn: E200033: sqlite[S5]: database is locked, executing statement 
'PRAGMA case_sensitive_like=1;PRAGMA synchronous=OFF;PRAGMA 
recursive_triggers=ON;PRAGMA foreign_keys=OFF;PRAGMA locking_mode 
= NORMAL;PRAGMA journal_mode = TRUNCATE;'

I'm running this in WSL (Windows 10 / Ubuntu 20.04.1 LTS). Is it supported?

All change indicators are gone from local modifications, I'm guessing VSCode changed their hooks?

Any help or direction on this would be greatly appreciated.