Skip to content

Enable Dependabot for NuGet and Docker#535

Open
naomizhengmsft wants to merge 1 commit into
mainfrom
chore/enable-dependabot
Open

Enable Dependabot for NuGet and Docker#535
naomizhengmsft wants to merge 1 commit into
mainfrom
chore/enable-dependabot

Conversation

@naomizhengmsft
Copy link
Copy Markdown
Member

Adds .github/dependabot.yml so future OSS vulnerabilities surface as automatic PRs instead of requiring manual remediation.

Coverage:

  • NuGet: weekly, recursive scan from repo root (all 7 csproj across both solutions). Minor and patch bumps grouped to reduce PR volume; majors still get individual PRs for breaking-change review.
  • Docker: weekly, root Dockerfile + .devcontainer/Dockerfile (separate entries because each Dockerfile location needs its own directive).

No github-actions ecosystem block because the repo has no workflows yet.

Follow-up to SFI-ES5.2 remediation: prevents the next round of transitive-vuln PRs from needing to be opened by hand.

@naomizhengmsft naomizhengmsft force-pushed the chore/enable-dependabot branch from 2d946c1 to 0778442 Compare June 4, 2026 12:49
Adds .github/dependabot.yml so future NuGet package version bumps surface as
scheduled PRs.

Be precise about scope — this enables ONE of the three independent Dependabot
features on GitHub:

  Enabled here: Dependabot version updates (scheduled, NuGet only).
                Weekly Mon 06:00 PT.

  NOT enabled here:
    - Dependabot alerts (already on by default for public repos).
    - Dependabot security updates (the reactive CVE-PR flow). That toggle
      lives in Settings -> Code security -> "Dependabot security updates"
      and is highly recommended as a separate follow-up — without it, CVE
      patches still get PR'd, but only on the weekly cadence below instead
      of within hours of advisory publication.
    - Docker ecosystem coverage. The repo has two Dockerfiles
      (root + .devcontainer) but base images are managed separately, so the
      docker ecosystem blocks are intentionally omitted. Re-add them if/when
      that policy changes.

Coverage of this file:
- NuGet: weekly, recursive scan from repo root (all 7 csproj across both
         solutions). Minor and patch bumps grouped to keep PR volume sane;
         majors still get individual PRs so breaking-change review stays
         explicit.

No github-actions ecosystem block because the repo has no workflows yet.

Follow-up to SFI-ES5.2 remediation: the manual transitive pins in that PR
(Microsoft.Bcl.Memory, System.Net.Http, System.Text.RegularExpressions)
are now direct PackageReferences, so future patches to those will get
auto-PR'd by this config.
@naomizhengmsft naomizhengmsft force-pushed the chore/enable-dependabot branch from 0778442 to 0277957 Compare June 5, 2026 20:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant