Repository navigation
ci: resubmit the NuGet dependency graph daily - #1331
Merged
Merged
Conversation
Dependabot matched GHSA-qhrr-8q5h-9q3h (MessagePack) against the submitted graph only when the next snapshot arrived: published 2026-10-15 18:35 UTC, alerted 2026-10-16 17:24 UTC. A daily run bounds that delay to a day when main has no dependency push. Refs #1291
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
1 participant
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.
#1291 proposed adding a workflow that submits the resolved NuGet graph.
.github/workflows/dependency-submission.ymlalready does that on dependency pushes tomain, and the SBOM lists about 400 NuGet packages, transitive ones included.What it lacked was a run when
maindoesn't change. MessagePack 2.5.302 was in the submitted graph, but GHSA-qhrr-8q5h-9q3h (published 2026-10-15 18:35 UTC) raised Dependabot alerts #27 and #28 only at 2026-10-16 17:24 UTC. That was the moment #1321's merge triggered a new snapshot. Until then, CI's restore gate was the only signal.This PR adds a daily run at 05:30 UTC, so a new advisory is matched within a day. The unchanged
correlatormakes each run replace the previous snapshot instead of adding to it. The #146 decision record notes the new trigger.Not covered: component-detection leaves out packages that the ASP.NET Core shared framework supplies, such as
System.Security.Cryptography.Xml. CI's--vulnerable --include-transitivegate and the weekly audit still catch those.Closes #1291