[release/v7.6.2] Remove package verification from the notice pipeline#27425
Merged
daxian-dbw merged 1 commit intoMay 13, 2026
Conversation
Contributor
There was a problem hiding this comment.
Pull request overview
Backport of #27289 to release/v7.6.2. Removes the now-redundant package license verification step from the notice pipeline since cgmanifest.json updates are handled by the Release Prep workflow.
Changes:
- Removed
SkipVerifyPackagesparameter and the ClearlyDefined verification step fromgenerateNotice.yml. - Removed the corresponding
SkipVerifyPackagesparameter and its passthrough fromapiscan-gen-notice.yml.
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 | Drops the SkipVerifyPackages parameter and the ClearlyDefined -TestAndHarvest verification step. |
| .pipelines/apiscan-gen-notice.yml | Removes the SkipVerifyPackages pipeline parameter and the value passed to the template. |
SeeminglyScience
approved these changes
May 13, 2026
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.6.2
Triggered by @daxian-dbw 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 the now-redundant package verification step from the notice pipeline since the Release Prep workflow already handles updating cgmanifest.json.
Customer Impact
Regression
REQUIRED: Check exactly one box.
This is not a regression.
Testing
Validated by the original PR. The package verification step is now handled by the Release Prep workflow, so removing it from the notice pipeline has no functional impact.
Risk
REQUIRED: Check exactly one box.
Removes a now-redundant step from the notice pipeline. The "Release Prep" workflow already handles updating cgmanifest.json, so removing package verification is a cleanup with no functional impact on the product.