diff --git a/.pipelines/vscode-powershell-OneBranch.yml b/.pipelines/vscode-powershell-OneBranch.yml
index 15a23dc60a..bebeb7ac58 100644
--- a/.pipelines/vscode-powershell-OneBranch.yml
+++ b/.pipelines/vscode-powershell-OneBranch.yml
@@ -54,7 +54,6 @@ extends:
       EnableCDPxPAT: false
       WindowsHostVersion:
         Version: 2022
-        Network: KS3
     release:
       category: NonAzure
     stages:
@@ -180,7 +179,7 @@ extends:
                 feed:
                   organization: msazure
                   project: One
-                  feedName: npmjs
+                  feedName: vsce
             steps:
               - pwsh: |
                   Write-Host Publishing: $(vsixVersion), pre-release: $(prerelease)
diff --git a/vscode-powershell.build.ps1 b/vscode-powershell.build.ps1
index 36c606cd18..e86987a0b7 100644
--- a/vscode-powershell.build.ps1
+++ b/vscode-powershell.build.ps1
@@ -71,12 +71,6 @@ task Build RestoreEditorServices, RestoreNode, {
     Write-Build DarkGreen "Building vscode-powershell"
     Assert-Build (Test-Path ./modules/PowerShellEditorServices/bin) "Extension requires PSES"
 
-    # TODO: When supported we should use `esbuild` for the tests too. Although
-    # we now use `esbuild` to transpile, bundle, and minify the extension, we
-    # still use `tsc` to transpile everything in `src` and `test` because the VS
-    # Code test runner expects individual files (and globs them at runtime).
-    # Unfortunately `esbuild` doesn't support emitting 1:1 files (yet).
-    # https://github.com/evanw/esbuild/issues/944
     switch ($Configuration) {
         "Debug" { Invoke-BuildExec { & npm run compile } }
         "Release" { Invoke-BuildExec { & npm run compile -- --minify } }