[release/v7.5] Integrate Windows packaging into windows-ci workflow using reusable workflow#26390
Merged
TravisEz13 merged 2 commits intoPowerShell:release/v7.5from Nov 5, 2025
Merged
Conversation
…orkflow (PowerShell#26224) Co-authored-by: copilot-swe-agent[bot] <[email protected]> Co-authored-by: TravisEz13 <[email protected]> Co-authored-by: Travis Plunk <[email protected]>
TravisEz13
added
the
CL-BuildPackaging
Contributor
There was a problem hiding this comment.
Pull Request Overview
This PR introduces a new reusable Windows packaging workflow that can be triggered conditionally in the Windows CI pipeline based on packaging-related file changes. The goal is to validate Windows packages on pull requests that modify packaging code without running the full packaging matrix on every CI run.
Key changes:
- Adds conditional Windows packaging job to CI that only runs when packaging files change
- Creates reusable packaging workflow with matrix strategy for multiple architectures and channels
- Updates path filter to detect packaging-related changes
Reviewed Changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated 3 comments.
| File | Description |
|---|---|
.github/workflows/windows-packaging-reusable.yml |
New reusable workflow defining Windows packaging matrix for x64/x86/arm64 architectures across preview and stable channels |
.github/workflows/windows-ci.yml |
Adds conditional packaging job and artifact directory environment variables |
.github/actions/infrastructure/path-filters/action.yml |
Adds packagingChanged output to detect changes to packaging-related files |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
daxian-dbw
approved these changes
Nov 5, 2025
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 #26224 to release/v7.5
Triggered by @TravisEz13 on behalf of @copilot
Original CL Label: CL-BuildPackaging
/cc @PowerShell/powershell-maintainers
Merge Conflicts
During the backport, merge conflicts were encountered in
.github/actions/infrastructure/path-filters/action.yml.Conflict details:
globalConfigChangedvariable that doesn't exist in release/v7.5Resolution:
globalConfigChangedfrom the packaging detection logicImpact
Tooling Impact
This PR integrates Windows packaging into the windows-ci workflow using a reusable workflow. It adds packaging change detection to path filters and creates a new reusable workflow for Windows packaging. This improves CI efficiency by only running packaging jobs when packaging-related files change.
Regression
This is not a regression fix. It's an improvement to the CI/CD pipeline.
Testing
The original PR was tested in the main branch CI pipeline. The backport maintains the same functionality, with the only difference being the removal of
globalConfigChangedreferences (which don't exist in v7.5). The packaging detection logic and workflow integration remain intact.Manual verification:
Risk
Medium risk - This change modifies the CI/CD pipeline by:
While the changes are well-contained and follow existing patterns, any CI/CD modifications carry inherent risk of affecting build and release processes. The conflict resolution required adaptation of the code for v7.5, which adds a small additional risk factor.