GitHub will disable Dependabot alerts on year-idle repositories
From 8 December, repos with no push, creation or alert-toggle activity in the past year lose Dependabot alerts automatically. Existing alerts are archived, not deleted.
GitHub announced on 10 November that Dependabot alerts will automatically switch off on repositories with no activity in the preceding twelve months, starting 8 December. Activity means a push to any branch or tag, creating the repository, or turning Dependabot alerts on, so most maintained projects are unaffected.
Existing alerts on an idle repo are archived rather than deleted, and restorable at any time. A single push to the repository turns alerts back on automatically and resets the twelve-month clock, or you can re-enable manually from repository settings. The change applies to every plan on github.com and GitHub Enterprise Cloud with data residency, but not Enterprise Server. Repos covered by an enforced security configuration, or an enterprise policy that locks Dependabot alerts on, are exempt.
Why it matters: if you have old repos lying around, forks you forgot about, side projects that are archived in spirit but not in settings, you’ll stop getting Dependabot alerts on them after 8 December unless something pushes to them. That’s fine for most of them, but worth checking now if you rely on a dormant repo’s alerts for compliance or monitoring.