[release/v7.6] Integrate Windows packaging into windows-ci workflow using reusable workflow #26468
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 #26224 to release/v7.6
Triggered by @TravisEz13 on behalf of @app/copilot-swe-agent
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 windows-ci to call the reusable packaging workflow and adds packaging path filters plus environment setup so the packaging automation continues to function on servicing branches.
Customer Impact
Shipping teams can only produce Windows packages when packaging jobs run; without this integration the release branch requires the deprecated AzDO pipeline, which slows servicing cadence.
Regression
REQUIRED: Check exactly one box.
This is not a regression.
Testing
Validated by rerunning the new Windows packaging reusable workflow on master, confirming each matrix leg (x64 preview, x86 stable, x86 preview, arm64 preview) builds and uploads artifacts; verified path-filter logic by touching packaging files and ensuring only the Windows packaging job fan-out triggered; smoke-ran Invoke-CIInstall/Invoke-CIFinish locally to ensure SBOM generation and artifact environment variables function outside AzDO.
Risk
REQUIRED: Check exactly one box.
Changes how all Windows packages are produced by moving the AzDO pipeline into GitHub Actions; any mistakes would block shipping signed MSI/MSIX payloads, so we treat this as high risk though the jobs are identical to master.