[release/v7.5.6] Separate Store Package Creation, Skip Polling for Store Publish, Clean up PDP-Media by daxian-dbw · Pull Request #27225 · PowerShell/PowerShell
Backport of #27024 to release/v7.5.6
Triggered by @daxian-dbw on behalf of @jshigetomi
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)
Refactors the store packaging and publish pipeline on release/v7.5.6 by separating StoreBroker package creation into its own template and stage, simplifying the MSIX pipeline and improving store publish reliability.
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 conflict in .pipelines/templates/package-create-msix.yml. Validation included confirming that package-create-msix.yml retains only msix bundle creation responsibilities, that the new package-store-package.yml template is present, and that backport PR CI will verify the full release pipeline behavior.
Risk
REQUIRED: Check exactly one box.
- High
- Medium
- Low
Medium risk because the change restructures release packaging and store publication workflows across multiple pipeline files, but the scope is limited to build/release infrastructure and the conflict resolution preserved the PR intent by removing obsolete in-template store package creation logic now moved to the new template.
Merge Conflicts
Conflict in .pipelines/templates/package-create-msix.yml. Cause: release/v7.5.6 still contained the older in-template StoreBroker package creation block, while PR #27024 moves that logic into the new .pipelines/templates/package-store-package.yml template. Resolution: removed the obsolete store packaging block from package-create-msix.yml, kept the msix bundle creation/sign/upload steps intact, and relied on the newly added template and stage changes from the cherry-pick for store package creation.