Agent Upstart

Cool things people are building with agents — and practical help getting the most out of them.

Playbooks · Coding

Dependabot pauses alerts on quiet repos

Written November 11, 2026

From December 8, 2026, GitHub turns off Dependabot alerts on most repositories with no activity in the past year. Your alerts are archived, not deleted — and any push brings them back.

The problem

A maintainer with old repositories will stop getting Dependabot alerts on December 8. The quiet inbox looks like a clean bill of health, but it means no new vulnerability alerts are arriving for those repos at all. The first thing to know is whether the alerts are gone or just paused, and how to get them back.

What changes on December 8

GitHub's changelog entry sets out the change plainly. Starting December 8, 2026, GitHub turns off Dependabot alerts on most repositories with no activity in the past year. Existing alerts are archived, not deleted, and can be restored at any time. The reason GitHub gives is scale: vulnerability discovery and alert volume are growing quickly, and pausing alerts on repos nobody touches keeps Dependabot fast and reliable for the repos under active development.

GitHub counts three things as activity: pushing to any branch or tag, creating the repository, and turning on Dependabot alerts. Any push to the repository turns alerts back on automatically. Alerts can also be turned back on in the repository's settings. Either way, GitHub restores the archived alerts, and the one-year clock starts over.

What is not affected

Two exceptions keep alerts running. GitHub will not turn off alerts on repositories with an enforced security configuration that enables Dependabot alerts. It also skips repositories in enterprises whose Dependabot alerts policy does not allow repository administrators to enable or disable alerts. The change applies to all plans on github.com and to GitHub Enterprise Cloud with data residency, where archived alerts stay in the same region as the rest of the enterprise's data. It does not apply to GitHub Enterprise Server.

What to do

If you have repositories you care about but have not touched in a year, do not wait for December 8 to find out which ones went quiet. Push a commit, or turn alerts back on in settings, before the pause takes effect — or accept the pause and know that a single push restores everything, archived alerts included. For repos you genuinely no longer maintain, the pause is harmless: nothing is deleted, and the alerts return the moment the repo becomes active again.

Limits

Related playbooks

Sources

Back to: Coding playbooks hub · Also: Dependabot now updates agent package managers · Git 2.56.1: patch the recursive-clone bug