Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Skip additional packages when generating component manifest #25102

Merged
merged 1 commit into from
Mar 11, 2025

Conversation

TravisEz13
Copy link
Member

@TravisEz13 TravisEz13 commented Feb 26, 2025

PR Summary

This pull request includes a small update to the tools/findMissingNotices.ps1 script. The change adds two new PowerShell modules to the list of modules being processed.

  • tools/findMissingNotices.ps1: Added Microsoft.PowerShell.GraphicalHost and Microsoft.PowerShell.CoreCLR.Eventing to the list of modules in the Get-CGRegistrations function.

PR Context

Our own components shouldn't be in the manifest.

PR Checklist

@TravisEz13 TravisEz13 added the CL-BuildPackaging Indicates that a PR should be marked as a build or packaging change in the Change Log label Mar 11, 2025
@TravisEz13
Copy link
Member Author

/azp run PowerShell-CI-linux-packaging, PowerShell-Windows-Packaging-CI

@TravisEz13 TravisEz13 enabled auto-merge (squash) March 11, 2025 20:25
Copy link

Azure Pipelines could not run because the pipeline triggers exclude this branch/path.

@TravisEz13 TravisEz13 merged commit 0fb7e3b into master Mar 11, 2025
35 checks passed
@microsoft-github-policy-service microsoft-github-policy-service bot removed the Review - Needed The PR is being reviewed label Mar 11, 2025
Copy link
Contributor

microsoft-github-policy-service bot commented Mar 11, 2025

📣 Hey @TravisEz13, how did we do? We would love to hear your feedback with the link below! 🗣️

🔗 https://aka.ms/PSRepoFeedback

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
BackPort-7.4.x-Done BackPort-7.5.x-Consider CL-BuildPackaging Indicates that a PR should be marked as a build or packaging change in the Change Log
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants