Native API deprecation tracking — beyond CVE-based Dependabot alerts

[Priyanka17solanki]

🏷️ Discussion Type

Product Feedback

💬 Feature/Topic Area

Dependabot

Discussion Details

Dependabot does a great job of flagging vulnerable library versions. But there's a gap: API deprecations within libraries that aren't security vulnerabilities.
If a library deprecates an internal method in v3.0 — not a CVE, just a breaking change — Dependabot stays silent. Your code continues using the deprecated API until something breaks in production.
Current workaround: CodeQL custom queries + scheduled GitHub Actions workflows. Buildable but requires custom setup and maintenance.
Feature request: A native "API lifecycle" tracking layer that scans your codebase for deprecated API usage and surfaces it alongside existing Dependabot alerts — monthly or on every PR.
This would complete the dependency security story from "is this library vulnerable?" to "is this library usage still supported?"

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐