-
Notifications
You must be signed in to change notification settings - Fork 8.2k
Open
Labels
Needs-TriageThe issue is new and needs to be triaged by a work group.The issue is new and needs to be triaged by a work group.WG-Maintainers-Buildspecific to affecting the buildspecific to affecting the buildWG-NeedsReviewNeeds a review by the labeled Working GroupNeeds a review by the labeled Working Group
Description
Prerequisites
- Write a descriptive title.
- Make sure you are able to repro it on the latest released version
- Search the existing issues.
- Refer to the FAQ.
- Refer to Differences between Windows PowerShell 5.1 and PowerShell.
Steps to reproduce
- wget https://aka.ms/pwsh-buildinfo-lts
- check Release tag that currently points to 7.4.12 even tho 7.4.13 is released since October 2025
- wget https://aka.ms/pwsh-buildinfo-stable seems also out of date
Expected behavior
$uri = 'https://aka.ms/pwsh-buildinfo-lts'
$expected = 'v7.4.13'
$info = Invoke-RestMethod -Uri $uri -Method Get -Headers @{ 'Accept' = 'application/json' }
if ($info.ReleaseTag -eq $expected) {
Write-Host "Yay we got 7.4.13!"
} else {
throw "Expected $expected but got $info.ReleaseTag"
}Actual behavior
Currently returns 7.4.12Error details
Environment data
Name Value
---- -----
PSVersion 5.1.26100.7653
PSEdition Desktop
PSCompatibleVersions {1.0, 2.0, 3.0, 4.0...}
BuildVersion 10.0.26100.7653
CLRVersion 4.0.30319.42000
WSManStackVersion 3.0
PSRemotingProtocolVersion 2.3
SerializationVersion 1.1.0.1Visuals
No response
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
Needs-TriageThe issue is new and needs to be triaged by a work group.The issue is new and needs to be triaged by a work group.WG-Maintainers-Buildspecific to affecting the buildspecific to affecting the buildWG-NeedsReviewNeeds a review by the labeled Working GroupNeeds a review by the labeled Working Group