-
Notifications
You must be signed in to change notification settings - Fork 731
Added PackageGuard to the build pipeline #3075
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
Added PackageGuard to the build pipeline #3075
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
This PR integrates PackageGuard into the build pipeline to perform package scanning and license validation. The change adds PackageGuard as a dependency scanning tool that validates package licenses against an allowlist configuration.
- Adds PackageGuard tool as a package dependency and configures it in the build system
- Creates a new
ScanPackagestarget that runs before thePacktarget to validate packages - Configures allowed licenses and packages through a JSON configuration file
Reviewed Changes
Copilot reviewed 5 out of 6 changed files in this pull request and generated 2 comments.
Show a summary per file
| File | Description |
|---|---|
| Build/_build.csproj | Adds PackageGuard as a package download dependency |
| Build/Build.cs | Implements ScanPackages target with GitHub API key parameter and tool configuration |
| .packageguard/config.json | Defines allowed licenses and packages for PackageGuard validation |
| .nuke/build.schema.json | Updates build schema to include new ScanPackages target and GitHubApiKey parameter |
| .github/workflows/build.yml | Provides GitHub token as GitHubApiKey environment variable for CI |
Pull Request Test Coverage Report for Build 16397565687Details
💛 - Coveralls |
Mostly as a way to dogfood PackageGuard on codebases with lots of different target frameworks and dependencies.