[release/v7.5.6] Change the display name of PowerShell-LTS package to PowerShell LTS#27223
Merged
daxian-dbw merged 1 commit intoApr 9, 2026
PowerShell:release/v7.5.6PowerShell/PowerShell:release/v7.5.6from
daxian-dbw:backport/release/v7.5.6/27203-0fe8748eadaxian-dbw/PowerShell:backport/release/v7.5.6/27203-0fe8748eaCopy head branch name to clipboard
Merged
[release/v7.5.6] Change the display name of PowerShell-LTS package to PowerShell LTS#27223daxian-dbw merged 1 commit intoPowerShell:release/v7.5.6PowerShell/PowerShell:release/v7.5.6from daxian-dbw:backport/release/v7.5.6/27203-0fe8748eadaxian-dbw/PowerShell:backport/release/v7.5.6/27203-0fe8748eaCopy head branch name to clipboard
daxian-dbw merged 1 commit into
PowerShell:release/v7.5.6PowerShell/PowerShell:release/v7.5.6from
daxian-dbw:backport/release/v7.5.6/27203-0fe8748eadaxian-dbw/PowerShell:backport/release/v7.5.6/27203-0fe8748eaCopy head branch name to clipboard
Conversation
Contributor
There was a problem hiding this comment.
Pull request overview
Updates MSIX packaging metadata on release/v7.5.6 so the PowerShell LTS package display name uses a space (“PowerShell LTS”) instead of a hyphen (“PowerShell-LTS”), improving presentation while keeping the package identity name unchanged.
Changes:
- Adjust MSIX
DisplayNameconstruction for LTS builds to append' LTS'instead of'-LTS'.
SeeminglyScience
approved these changes
Apr 9, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Backport of #27203 to release/v7.5.6
Triggered by @daxian-dbw on behalf of @daxian-dbw
Original CL Label: CL-BuildPackaging
/cc @PowerShell/powershell-maintainers
Impact
REQUIRED: Choose either Tooling Impact or Customer Impact (or both). At least one checkbox must be selected.
Tooling Impact
Updates the PowerShell-LTS package display name in packaging metadata for the release branch. This improves store/package presentation and consistency but is not required for build correctness.
Customer Impact
Regression
REQUIRED: Check exactly one box.
This is not a regression.
Testing
Cherry-pick applied cleanly to release/v7.5.6. The change is a narrow packaging metadata update in tools/packaging/packaging.psm1 and validation will rely on backport PR CI for the release branch.
Risk
REQUIRED: Check exactly one box.
Low risk because the change only adjusts the package display name while preserving package identity and does not alter runtime behavior or packaging flow.