[release/v7.5.7] Remove package verification from the notice pipeline#27463
Open
adityapatwardhan wants to merge 1 commit into
Open
Conversation
Contributor
There was a problem hiding this comment.
Pull request overview
This PR backports the notice-pipeline simplification to release/v7.5.7, keeping the APIScan/notice pipeline focused on generating and uploading notices after package verification moved elsewhere.
Changes:
- Removes the
SkipVerifyPackagespipeline/template parameter. - Removes the
ClearlyDefined.ps1 -TestAndHarvestpackage license verification step from notice generation.
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 package verification parameter and step from the notice job. |
.pipelines/apiscan-gen-notice.yml |
Removes the now-unused top-level parameter and template argument. |
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.5.7
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 package verification from the notice pipeline, as this is now handled by the Release Prep workflow. Keeps the pipeline focused and avoids redundant checks.
Customer Impact
Regression
REQUIRED: Check exactly one box.
This is not a regression.
Testing
Cherry-pick applied cleanly onto release/v7.5.7 with no conflicts. Verified branch commit and push succeeded. The change scope is limited to pipeline YAML logic.
Risk
REQUIRED: Check exactly one box.
Change is limited to build pipeline logic. No impact on runtime or customer-facing code. Ensures pipelines are functional and not redundant.