[release/v7.4.16] Remove package verification from the notice pipeline#27429
Merged
adityapatwardhan merged 1 commit intoMay 15, 2026
Conversation
Contributor
There was a problem hiding this comment.
Pull request overview
This PR backports the change from #27289 to release/v7.4.16, removing the package/license verification step from the NOTICE generation pipeline now that the Release Prep workflow handles cgmanifest.json updates.
Changes:
- Removed the
SkipVerifyPackagesparameter from the NOTICE-generation template and its callers. - Dropped the ClearlyDefined
-TestAndHarvestverification step from the NOTICE pipeline job.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
.pipelines/templates/compliance/generateNotice.yml |
Removes the optional package verification parameter and the ClearlyDefined verification step from the NOTICE generation job. |
.pipelines/apiscan-gen-notice.yml |
Removes the unused SkipVerifyPackages parameter and stops passing it into the NOTICE template. |
andyleejordan
approved these changes
May 14, 2026
3dc4808
into
PowerShell:release/v7.4.16
40 checks passed
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 #27289 to release/v7.4.16
Triggered by @adityapatwardhan 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
Removes unnecessary verification step from CI pipeline. Ensures pipeline is up-to-date with current release process.
Customer Impact
Regression
REQUIRED: Check exactly one box.
This is not a regression.
Testing
Validated pipeline changes by running the updated workflow. No failures observed and cgmanifest updates are handled by Release Prep workflow.
Risk
REQUIRED: Check exactly one box.
This change only removes redundant package verification from the notice pipeline, which is now handled elsewhere. No impact on product code or customer scenarios.