AUXSAYS Tactical knowledge for creators who want control
< Back to GitHub
GitHub / Copilot logo GitHub / Copilot GitHub

Patch intelligence record

GitHub / Copilot Dependabot alerts will pause on inactive repositories

ProductGitHub / Copilot VersionDependabot alerts will pause on inactive repositories Release dateNov 10, 2026
AUXSAYS verdict INSUFFICIENT DATA

AUXSAYS is not monitoring community reports for this product.

Community signal: Not monitored 0 confirmed patch-specific community reports

Community consensus not established.

Monitoring OFFICIAL SOURCE ONLY no run recorded Collection detail
Vendor Known Issues — No vendor-known issue data captured for this patch.

AUXSAYS has not captured official issue data for this patch. This does not indicate the vendor has no issues. Not counted as community reports.

Official Patch Notes — vendor release notes captured from the official source

Starting December 8, 2026, GitHub will turn off Dependabot alerts on most repositories with no activity in the past year. Their existing alerts are archived, not deleted, and you can restore them at any time. With vulnerability discovery and alert volume growing quickly, this keeps Dependabot fast and reliable for the repositories you’re actively developing. What counts as activity GitHub counts any of these as activity: Pushing to any branch or tag Creating the repository Turning on Dependabot alerts Turn alerts back on Any push to the repository automatically turns Dependabot alerts back on. You can also turn them on in the repository’s settings . Either way, GitHub restores the archived alerts, and the one-year clock starts over. Keep alerts on regardless of activity GitHub won’t turn off alerts on repositories with an enforced security configuration that enables Dependabot alerts. It also skips repositories in enterprises whose Dependabot alerts policy doesn’t allow repository administrators to enable or disable alerts. This change applies to all plans on github.com and to GitHub Enterprise Cloud with data residency. For data residency customers, archived alerts are stored in the same region as the rest of your enterprise’s data. It doesn’t apply to GitHub Enterprise Server. The post Dependabot alerts will pause on inactive repositories appeared first on The GitHub Blog .

Starting December 8, 2026, GitHub will turn off Dependabot alerts on most repositories with no activity in the past year. Their existing alerts are archived, not deleted, and you can restore them at any time. With vulnerability discovery and alert volume growing quickly, this keeps Dependabot fast and reliable for the repositories you’re actively developing.

What counts as activity GitHub counts any of these as activity:

Pushing to any branch or tag Creating the repository Turning on Dependabot alerts

Turn alerts back on Any push to the repository automatically turns Dependabot alerts back on. You can also turn them on in the repository’s settings . Either way, GitHub restores the archived alerts, and the one-year clock starts over.

Keep alerts on regardless of activity GitHub won’t turn off alerts on repositories with an enforced security configuration that enables Dependabot alerts. It also skips repositories in enterprises whose Dependabot alerts policy doesn’t allow repository administrators to enable or disable alerts.

This change applies to all plans on github.com and to GitHub Enterprise Cloud with data residency. For data residency customers, archived alerts are stored in the same region as the rest of your enterprise’s data. It doesn’t apply to GitHub Enterprise Server.

The post Dependabot alerts will pause on inactive repositories appeared first on The GitHub Blog .

Collection Health
Community monitoring OFFICIAL SOURCE ONLY
Accepted reports
0
Latest evidence run
Not recorded
Healthy sources
0 fresh (success / no reports) · need 2

Monitoring reflects community-evidence collection health for this exact release — an absence of reports is not a safety guarantee, and this is separate from the AUXSAYS verdict.

Technical Details
Released
Nov 10, 2026
Official source checked
Nov 11, 2026
Official notes checked
Nov 11, 2026
User Reports / Sources (0)

No user report sources have been counted for this record yet.

Official sources