AU: 1 updated - vscode-ansible

[skip ci] https://gist.github.com/675e3f672bda54270f8d7f5415f9374d/ecf6ef345f45068fd4eb3bd84449e3a53ae33f5a

automatic/vscode-ansible/tools/chocolateyInstall.ps1

@@ -1,3 +1,3 @@
 $ErrorActionPreference = 'Stop'
 
-Install-VsCodeExtension -extensionId 'vscoss.vscode-ansible@0.5.2'
+Install-VsCodeExtension -extensionId 'vscoss.vscode-ansible@0.6.0'

automatic/vscode-ansible/vscode-ansible.nuspec

@@ -26,7 +26,7 @@ This is a nuspec. It mostly adheres to https://docs.nuget.org/create/Nuspec-Refe
     <!-- version should MATCH as closely as possible with the underlying software -->
     <!-- Is the version a prerelease of a version? https://docs.nuget.org/create/versioning#creating-prerelease-packages -->
     <!-- Note that unstable versions like 0.0.1 can be considered a released version, but it's possible that one can release a 0.0.1-beta before you release a 0.0.1 version. If the version number is final, that is considered a released version and not a prerelease. -->
-    <version>0.5.2</version>
+    <version>0.6.0</version>
     <!-- owners is a poor name for maintainers of the package. It sticks around by this name for compatibility reasons. It basically means you. -->
     <owners>Maurice Kevenaar</owners>
     <!-- ============================== -->
@@ -62,7 +62,7 @@ let them know the package is no longer updating correctly.
     <!-- Specifying dependencies and version ranges? https://docs.nuget.org/create/versioning#specifying-version-ranges-in-.nuspec-files -->
     <dependencies>
       <dependency id="chocolatey-vscode.extension" version="1.0.0" />
-      <dependency id="vscode" version="1.30.0" />
+      <dependency id="vscode" version="1.31.0" />
     </dependencies>
 
     <!--<provides>NOT YET IMPLEMENTED</provides>-->