[release/v7.6] Move package validation to package pipeline #26558
+7
−8
Conversation
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
adityapatwardhan
added
the
CL-BuildPackaging
Contributor
There was a problem hiding this comment.
Pull request overview
This PR backports changes from #26414 to move package validation from the release pipeline to the package pipeline, ensuring validation occurs earlier in the CI/CD process. This improves the sequencing of operations by validating packages immediately after they are uploaded to blob storage, rather than waiting for the release pipeline to start.
Key Changes:
- Relocated the
validatePackagesstage from release pipeline to package pipeline - Updated stage dependencies to maintain correct execution order
- Minor formatting improvement (trailing whitespace removal)
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
.pipelines/PowerShell-Release-Official.yml |
Removed validatePackages stage and its dependency reference from UpdateChangeLog stage; fixed trailing whitespace |
.pipelines/PowerShell-Packages-Official.yml |
Added validatePackages stage with dependency on upload stage to validate packages immediately after upload |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
daxian-dbw
approved these changes
Dec 2, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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 #26414 to release/v7.6
Triggered by @adityapatwardhan on behalf of @TravisEz13
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
This change moves package validation from the release pipeline to the package pipeline, improving sequencing and ensuring validation occurs earlier in the process. This is required to maintain proper build pipeline functionality on the release branch.
Customer Impact
Regression
REQUIRED: Check exactly one box.
This is not a regression.
Testing
Original PR was validated through CI pipeline testing. Change affects build/release automation and has been running successfully on main branch. Backport verified by cherry-pick success and will be validated through CI on the release branch.
Risk
REQUIRED: Check exactly one box.
Medium risk because this changes CI/CD pipeline structure, but the change is well-tested on main branch and is necessary to maintain pipeline consistency across branches. The risk is mitigated by the fact that this only moves validation to an earlier stage, reducing overall complexity.