Repository navigation
ci: classify routine dependency updates without asserting vulnerabilities - #121
Merged
Merged
Conversation
The dependency intake configuration now classifies routine NuGet updates as maintenance work. Both update ecosystems assign milestone five by default. These defaults provide a release qualification queue without asserting a confirmed vulnerability. The engineering guide explains escalation for an actual security advisory. A maintainer links the security issue and selects its G1 milestone and security labels. The first automated batch has a dedicated qualification issue. This change alters routing metadata and documentation only. It does not update or merge any dependency. Seventeen metadata tests passed, and 123 Markdown files passed the documentation checker. Independent review found no material issue. Changed files: - ".github/dependabot.yml" (+3/-1 lines). - "docs/engineering.md" (+4/-0 lines). The file counts compare the staged tree with its first parent. Refs: #11, #18, #120. Staged-Tree: 2251b79
Codex Review Summary: ✅ CompletedThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
This was referenced Nov 10, 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.
Problem
The first automated NuGet update batch inherited blanket security labels. A routine version proposal does not establish a vulnerability. Both update ecosystems also need a default delivery milestone.
Changes
Set neutral type:process and area:release labels for routine NuGet updates. Assign milestone 5 to GitHub Actions and NuGet intake. Document manual escalation to the relevant G1 issue and security labels when an advisory is confirmed. Preserve the original automated PR release notes; qualify the first five proposals separately under #120.
Verification
Local: 17 metadata tests passed, the documentation checker verified 123 Markdown files with zero errors, and git diff --check passed. A fresh independent review found no material issue in the two-file delta. Hosted CI and CodeQL passed on final head
ed38d4e86daf0d9a46cb5ca4d0ac12dcd9fb6a60: secrets, libraries, gui, tools, governance, C# and Python analysis and the CodeQL result check succeeded. The required Contribution metadata status also passed. Superseded metadata job cancellations came from concurrent metadata events; the final status must remain successful before integration. The active worker created PRs #112–#116; this provides actual intake evidence, not compatibility acceptance.Risk and recovery
Risk: Medium. This changes routing metadata and documentation, with no dependency version or product code change. Revert this configuration if intake routing is wrong. A maintainer must reclassify confirmed security advisories during triage because custom Dependabot labels apply to security updates too. The dependency PRs remain unmerged and require their own review and exact-head checks.
Related work
Refs #11, #18 and #120. Audit index #21. The initial governance package was integrated through #111. Main branch protection is active with nine app-bound required contexts, current-base checks, required PRs, resolved conversations and administrator enforcement. Force pushes and deletion are prohibited. This PR must merge through those rules.