Upload assets to release

Author: andyleejordan

docs/development.md

@@ -140,6 +140,5 @@ use the same code which includes dependencies).
 * `Update-Changelog` could be faster by not downloading _every_ PR
 * `Update-Changelog` should use exactly two emoji and in the right order
 * `Update-Version` could be run by `Update-Changelog`
-* `New-DraftRelease` could automatically set the tag pointers and upload the binaries
 * The build should emit an appropriately named VSIX instead of us manually renaming it
 * A `Publish-Binaries` function could be written to push the binaries out

tools/ReleaseTools.psm1

@@ -342,7 +342,10 @@ function New-DraftRelease {
     param(
         [Parameter(Mandatory)]
         [ValidateSet([RepoNames])]
-        [string]$RepositoryName
+        [string]$RepositoryName,
+
+        [Parameter(ValueFromPipeline)]
+        [string[]]$Assets
     )
     $Version = Get-Version -RepositoryName $RepositoryName
     $Changelog = (Get-FirstChangelog -RepositoryName $RepositoryName) -join "`n"
@@ -354,8 +357,10 @@ function New-DraftRelease {
         Name       = "v$Version"
         Body       = $ChangeLog
         PreRelease = [bool]$Version.PreReleaseLabel
+        OwnerName  = "PowerShell"
+        RepositoryName = $RepositoryName
     }
 
-    Get-GitHubRepository -OwnerName PowerShell -RepositoryName $RepositoryName |
-        New-GitHubRelease @ReleaseParams
+    $Release = New-GitHubRelease @ReleaseParams
+    $Assets | New-GitHubReleaseAsset -Release $Release.Id
 }