Add New-Release to ReleaseTools module

Author: andyleejordan

docs/development.md

@@ -65,9 +65,8 @@ Microsoft. The comments are manual steps.
 
 ```powershell
 Import-Module ./tools/ReleaseTools.psm1
-Update-Changelog -RepositoryName PowerShellEditorServices -Version <version>
-Update-Changelog -RepositoryName vscode-powershell -Version <version>
-# Amend changelog as necessary, open PR
+New-Release -PsesVersion <version> -VsceVersion <version>
+# Amend changelog as necessary
 # Push release branches to ADO
 # Permit both pipelines to draft GitHub releases
 # Download and test assets

tools/ReleaseTools.psm1

@@ -278,8 +278,6 @@ function Update-Changelog {
             git commit -m "Update CHANGELOG for ``$Version``"
         }
     }
-
-    Update-Version -RepositoryName $RepositoryName
 }
 
 <#
@@ -304,6 +302,7 @@ function Update-Changelog {
     - `name` field has `-preview` appended similarly
     - `displayName` field has ` Preview` appended similarly
     - `description` field has `(Preview) ` prepended similarly
+    - `icon` field has `_Preview ` inserted similarly
 #>
 function Update-Version {
     [CmdletBinding(SupportsShouldProcess)]
@@ -369,8 +368,6 @@ function Update-Version {
             git commit -m "Bump version to ``v$Version``"
         } # TODO: Git reset to unstage
     }
-
-    New-ReleasePR -RepositoryName $RepositoryName
 }
 
 <#
@@ -416,6 +413,45 @@ function New-ReleasePR {
     $Repo | Add-GitHubIssueLabel -Issue $PR.PullRequestNumber -LabelName "Ignore"
 }
 
+<#
+.SYNOPSIS
+  Kicks off the whole release process.
+.DESCRIPTION
+  This first updates the changelog (which creates and checks out the `release`
+  branch), commits the changes, updates the version (and commits), pushes the
+  branch, and then creates a GitHub PR for the release for both repositories.
+
+  This is the function meant to be called by a maintainer as the first manual
+  step to creating a release: it calls the correct functions in order to prepare
+  the release. Each repository's release branch then needs to be pushed to the
+  internal Azure DevOps mirror, at which point the automatic release pipeline
+  will build and sign the assets, and queue up draft GitHub releases (using
+  `New-DraftRelease` below). Those releases need to be manually validated and
+  approved, and finally the last step is to approve the pipeline to publish the
+  assets to the marketplace and gallery.
+#>
+function New-Release {
+    [CmdletBinding(SupportsShouldProcess)]
+    param(
+        [Parameter(Mandatory)]
+        [ValidateScript({ $_.StartsWith("v") })]
+        [string]$PsesVersion,
+
+        [Parameter(Mandatory)]
+        [ValidateScript({ $_.StartsWith("v") })]
+        [string]$VsceVersion
+    )
+    "PowerShellEditorServices", "vscode-powershell" | ForEach-Object {
+        $Version = switch ($_) {
+            "PowerShellEditorServices" { $PsesVersion }
+            "vscode-powershell" { $VsceVersion }
+        }
+        Update-Changelog -RepositoryName $_ -Version $Version
+        Update-Version -RepositoryName $_
+        New-ReleasePR -RepositoryName $_
+    }
+}
+
 <#
 .SYNOPSIS
   Creates a new draft GitHub release and Git tag from the updated changelog.