Skip to content

ci: classify routine dependency updates without asserting vulnerabilities - #121

Merged
lumenpearson merged 1 commit into
mainfrom
dev/dependency-intake-classification
Nov 10, 2026
Merged

lumenpearson merged 1 commit into
mainfrom
dev/dependency-intake-classification

Conversation

@lumenpearson

@lumenpearson lumenpearson commented Nov 10, 2026 •

Copy link
Copy Markdown
Owner

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.

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
@lumenpearson lumenpearson added type:process Change delivery rules, tracking or engineering automation. area:release MSI, portable layout, update, signatures and release qualification. labels Nov 10, 2026 — with ChatGPT Codex Connector
@lumenpearson lumenpearson self-assigned this Nov 10, 2026
@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Nov 10, 2026 •

Copy link
Copy Markdown
Codex Review Summary: ✅ Completed

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-11-10T17:10:53.413588Z ed38d4e PR opened
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@lumenpearson
lumenpearson merged commit 6a54391 into main Nov 10, 2026
18 of 19 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area:release MSI, portable layout, update, signatures and release qualification. type:process Change delivery rules, tracking or engineering automation.

Projects

Development

Successfully merging this pull request may close these issues.

1 participant