[Ignore] Marketplace doesn't support SemVer, npm ONLY supports SemVer (#1718)

* Marketplace doesn't support SemVer, npm ONLY supports SemVer

* update doc

* save new version to PackageJson

Author: TylerLeonhardt

docs/development.md

@@ -49,7 +49,7 @@ code --extensionDevelopmentPath="c:\path\to\vscode-powershell" .
 
 To build a preview version of the extension, that is to say,
 a version of the extension named "PowerShell Preview",
-You can simply change the version in the package.json to include `-preview` at the end.
+You can simply change the `name` in the package.json to include `-Preview` at the end.
 When you build, this will:
 
 - Add a warning to the top of the README.md to warn users not to have the stable and preview version enabled at the same time

package.json

@@ -1,7 +1,7 @@
 {
   "name": "PowerShell-Preview",
   "displayName": "PowerShell Preview",
-  "version": "2.0.0-preview.1",
+  "version": "2.0.0",
   "preview": true,
   "publisher": "ms-vscode",
   "description": "(Preview) Develop PowerShell scripts in Visual Studio Code!",

vscode-powershell.build.ps1

@@ -32,6 +32,7 @@ task GetExtensionData -Before Package {
 
     if ($updateVersion) {
         exec { & npm version $script:ExtensionVersion --no-git-tag-version --allow-same-version }
+        $script:PackageJson.version = $script:ExtensionVersion
     }
 
     $script:ExtensionName = $script:PackageJson.name
@@ -111,7 +112,7 @@ task Test Build, {
     }
 }
 
-task CheckPreview -If { $script:ExtensionVersion -like "*preview*" } `
+task CheckPreview -If { $script:ExtensionName -like "*Preview*" } `
     UpdateReadme, UpdatePackageJson
 
 task UpdateReadme {