[release/v7.5.6] Build, package, and create VPack for the PowerShell-LTS store package within the same `msixbundle-vpack` pipeline (#150) by daxian-dbw · Pull Request #27240 · PowerShell/PowerShell
Backport of #27209 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
- Required tooling change
- Optional tooling change (include reasoning)
Updates the release/v7.5.6 VPack pipeline so the PowerShell-LTS store package is built, packaged, and prepared for VPack creation within the same official pipeline, including related packaging and symbol publication changes required for compliance.
Customer Impact
- Customer reported
- Found internally
Regression
REQUIRED: Check exactly one box.
- Yes
- No
This is not a regression.
Testing
Cherry-pick completed on release/v7.5.6 after resolving one resource-file conflict in TabCompletionStrings.resx. Validation included confirming the incoming resource entries were preserved, all conflict markers were removed, and the remaining changes applied cleanly across the pipeline, packaging, and source files. Release branch CI will provide end-to-end verification.
Risk
REQUIRED: Check exactly one box.
- High
- Medium
- Low
Medium risk because the change touches official packaging pipeline configuration and several packaging-related source files, but the conflict resolution was narrowly scoped to a single .resx resource block and the overall backport remains aligned with the original PR intent.
Merge Conflicts
Conflict in src/System.Management.Automation/resources/TabCompletionStrings.resx. Cause: the target release branch and the original PR both changed the same resource region. Resolution: accepted the incoming PR resource entries and preserved the surrounding release branch file structure.