Conversation
|
/azp run PowerShell-CI-macos |
|
/azp run PowerShell-CI-linux |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run PowerShell-CI-windows |
|
Azure Pipelines successfully started running 1 pipeline(s). |
1 similar comment
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run PowerShell-static-analysis |
|
No pipelines are associated with this pull request. |
|
/azp run PowerShell-Windows-Packaging-CI |
|
Azure Pipelines could not run because the pipeline triggers exclude this branch/path. |
|
/azp run PSResourceGet ACR |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run PowerShell-CI-static-analysis |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run PowerShell-CI-linux |
|
/azp run PowerShell-CI-macos |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run PowerShell-CI-windows |
|
Azure Pipelines successfully started running 1 pipeline(s). |
1 similar comment
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run PSResourceGet ACR |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run PowerShell-CI-static-analysis |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run PowerShell-Windows-Packaging-CI |
|
Azure Pipelines could not run because the pipeline triggers exclude this branch/path. |
|
/azp run PowerShell-CI-linux |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run PowerShell-CI-linux |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
📣 Hey @jshigetomi, how did we do? We would love to hear your feedback with the link below! 🗣️ 🔗 https://aka.ms/PSRepoFeedback |
|
@jshigetomi, since the PR was merged the "https://aka.ms/install-powershell.ps1" script fails when run on a Windows ARM64 machine with the following arguments: $installScript = "$env:TEMP\install-powershell.ps1"
Invoke-WebRequest -Uri "https://aka.ms/install-powershell.ps1" -OutFile $installScript
& $installScript -AddToPathAn exception is thrown saying the following URL is 404-ing: Comes from line 374 in the script: $metadata = Invoke-RestMethod https://raw.githubusercontent.com/PowerShell/PowerShell/master/tools/metadata.json
if ($Preview) {
$release = $metadata.PreviewReleaseTag -replace '^v'
} else {
$release = $metadata.ReleaseTag -replace '^v'
}
if ($IsWinEnv) {
if ($UseMSI) {
$packageName = "PowerShell-${release}-win-${architecture}.msi"
} else {
$packageName = "PowerShell-${release}-win-${architecture}.zip"
}
} elseif ($IsLinuxEnv) {
$packageName = "powershell-${release}-linux-${architecture}.tar.gz"
} elseif ($IsMacOSEnv) {
$packageName = "powershell-${release}-osx-${architecture}.tar.gz"
}
$downloadURL = "https://github.com/PowerShell/PowerShell/releases/download/v${release}/${packageName}"
Write-Verbose "About to download package from '$downloadURL'" -Verbose
$packagePath = Join-Path -Path $tempDir -ChildPath $packageName
if (!$PSVersionTable.ContainsKey('PSEdition') -or $PSVersionTable.PSEdition -eq "Desktop") {
# On Windows PowerShell, progress can make the download significantly slower
$oldProgressPreference = $ProgressPreference
$ProgressPreference = "SilentlyContinue"
}
try {
**** Invoke-WebRequest -Uri $downloadURL -OutFile $packagePath ****
} finally {
if (!$PSVersionTable.ContainsKey('PSEdition') -or $PSVersionTable.PSEdition -eq "Desktop") {
$ProgressPreference = $oldProgressPreference
}
} |
PR Summary
This pull request updates the release tags in the
tools/metadata.jsonfile to reflect the latest versions.Release tag updates:
PreviewReleaseTagfromv7.5.0-rc.1tov7.6.0-preview.2.ReleaseTagfromv7.4.6tov7.6.0-preview.2.NextReleaseTagfromv7.5.0-preview.6tov7.6.0-preview.3.PR Context
PR Checklist
.h,.cpp,.cs,.ps1and.psm1files have the correct copyright headerWIP:or[ WIP ]to the beginning of the title (theWIPbot will keep its status check atPendingwhile the prefix is present) and remove the prefix when the PR is ready.- [ ] Issue filed:
(which runs in a different PS Host).