Add Publish-Assets function to ReleaseTools module

Author: andyleejordan

docs/development.md

@@ -77,9 +77,7 @@ New-DraftRelease -RepositoryName PowerShellEditorServices -Assets "PowerShellEdi
 New-DraftRelease -RepositoryName vscode-powershell -Assets "powershell-YYYY.M.X.vsix", "Install-VSCode.ps1"
 # Check telemetry for stability before releasing
 # Publish draft releases and merge (don't squash!) branches
-vsce publish --packagePath ./PowerShell-<version>.vsix
-# Update Install-VSCode.ps1 on gallery
-Publish-Script -Path ./Install-VSCode.ps1 -NuGetApiKey (Get-Secret "PowerShell Gallery API Key" -AsPlainText)
+# Permit release pipeline to publish assets
 ```
 
 ### Versioning
@@ -135,4 +133,3 @@ use the same code which includes dependencies).
 * `Update-Changelog` should verify the version is in the correct format
 * `Update-Changelog` could be faster by not downloading _every_ PR
 * `Update-Version` could be run by `Update-Changelog`
-* A `Publish-Binaries` function could be written to push the binaries out

tools/ReleaseTools.psm1

@@ -151,7 +151,7 @@ function Update-Branch {
 
 <#
 .SYNOPSIS
-  Gets current version from changelog as [semver].
+  Gets current version from changelog as `[semver]`.
 #>
 function Get-Version {
     param(
@@ -173,7 +173,7 @@ function Get-Version {
   Updates the CHANGELOG file with PRs merged since the last release.
 .DESCRIPTION
   Uses the local Git repositories but does not pull, so ensure HEAD is where
-  you want it. Creates a new branch at 'release/$Version' if not already
+  you want it. Creates a new branch at `release/$Version` if not already
   checked out. Handles any merge option for PRs, but is a little slow as it
   queries all PRs.
 #>
@@ -366,3 +366,42 @@ function New-DraftRelease {
     Write-Output "Uploading assets..."
     $Assets | New-GitHubReleaseAsset -Release $Release.Id
 }
+
+<#
+.SYNOPSIS
+  Uploads VSIX and PS1 binaries to their respective marketplaces.
+.DESCRIPTION
+  The VSIX is uploaded to the Visual Studio Code Marketplace using the `vsce`
+  tool and the `VsceToken` parameter:
+  https://marketplace.visualstudio.com/VSCode
+
+  The PS1 is uploaded to the PowerShell Gallery using the `Publish-Script`
+  cmdlet and the `GalleryToken` parameter: https://www.powershellgallery.com
+
+  This function is primarily used by ADO pipelines, but could be used manually.
+#>
+function Publish-Assets {
+    param(
+        [Parameter(Mandatory)]
+        [string[]]$Assets,
+
+        [Parameter()]
+        [string]$VsceToken,
+
+        [Parameter()]
+        [string]$GalleryToken
+    )
+    switch ($Assets) {
+        { $_.EndsWith(".vsix") } {
+            Write-Output "Uploading VSIX..."
+            vsce publish --packagePath $_ --pat $VsceToken
+        }
+        { $_.EndsWith(".ps1") } {
+            Write-Output "Uploading PS1..."
+            Publish-Script -Path $_ -NuGetApiKey $GalleryToken
+        }
+        default {
+            Write-Error "Unsupported file: $_"
+        }
+    }
+}