You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit a6655b0
Browse filesBrowse the repository at this point in the historyBrowse files
feat(ci): alert sweep tracks advisories with no patched release
An open Dependabot alert whose advisory lists no first_patched_version
was skipped, so a newly disclosed vulnerability with no fix yet filed no
issue. It now stays in its (package, manifest) group:
- When no applying advisory has a fix, the issue asks for a decision
(mitigate, pin away, drop, accept) instead of a bump; the marker
records fixed=none.
- When others do, the bump issue carries a "No patched release" section
for the unpatched advisories whose range still covers the target.
- A patched release published later rewrites the same issue into a bump
in place, since the marker is keyed on package and manifest.
An advisory that loses its patched version now rewrites its issue to ask
for a decision rather than leaving it as is; it still never stands the
issue down.
Closesmodelcontextprotocol#5066
Co-Authored-By: Claude Opus 5.5 <[email protected]>
Signed-off-by: cliffhall <[email protected]>
|`dependency-refresh.yml` → `scripts/dependency-refresh.mjs`|`.github/dependabot.yml` (deleted) |**One** tracking issue: `npm outdated` across the root and workspaces, each Python server's `uv lock --upgrade` dry run, and each workflow `uses:` ref against its action's highest release | Monthly |
217
-
|`dependabot-alerts.yml` → `scripts/dependabot-alerts.mjs`| Security-update PRs (the `automated-security-fixes`**repo setting**, off) | One issue per vulnerable package per lockfile (npm and pip) that has a patched release, targeting the lowest patched version outside every applicable range, or flagging that no listed fix clears them all | Daily |
218
-
|`sdk-watch.yml` → `scripts/sdk-watch.mjs`| Nothing: SDK releases were watched by habit | One issue per MCP SDK group behind its registry (npm `@modelcontextprotocol/*`, PyPI `mcp`), plus a Claude analysis comment | Nightly |
|`dependency-refresh.yml` → `scripts/dependency-refresh.mjs`|`.github/dependabot.yml` (deleted) |**One** tracking issue: `npm outdated` across the root and workspaces, each Python server's `uv lock --upgrade` dry run, and each workflow `uses:` ref against its action's highest release | Monthly |
217
+
|`dependabot-alerts.yml` → `scripts/dependabot-alerts.mjs`| Security-update PRs (the `automated-security-fixes`**repo setting**, off) | One issue per vulnerable package per lockfile (npm and pip), targeting the lowest patched version outside every applicable range, flagging that no listed fix clears them all, or asking for a decision on an advisory with no patched release| Daily |
218
+
|`sdk-watch.yml` → `scripts/sdk-watch.mjs`| Nothing: SDK releases were watched by habit | One issue per MCP SDK group behind its registry (npm `@modelcontextprotocol/*`, PyPI `mcp`), plus a Claude analysis comment | Nightly |
219
219
220
220
-**Never re-add `.github/dependabot.yml` or switch `automated-security-fixes`
221
221
back on.** Keep Dependabot **alerts** on: the alert sweep consumes them. The
0 commit comments