305-bug-fix-nuget-package-reference-check-false-positive-issue-notifications#306
Open
omranatstarion wants to merge 2 commits into
Conversation
…-check.yml to not flqg the non updated transient packages but well log them
5 tasks
antoineatstariongroup
approved these changes
Jun 11, 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.



Prerequisites
Description
This pull request improves the existing NuGet package reference check workflow.
The outdated package check now keeps transitive outdated packages visible in the GitHub Actions logs, but only uses direct/top-level outdated packages for GitHub issue creation. This avoids polluting the repository issues with transitive package updates that are usually not directly actionable.
Deprecated and vulnerable package checks still include transitive packages, since those can still affect the project even when they are not referenced directly.
The workflow also keeps the safer issue synchronization behavior:
.Testsproject sections from the generated issue output