Dependency Graph dependents are wrong #171055
Replies: 1 comment
-
|
💬 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 ⏩
Where to look to see what's shipping 👀
What you can do in the meantime 💻
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. ⭐ |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Select Topic Area
Bug
Body
I have a package that I'm looking to retire. I took a quick glance at the Dependents of the package from github's dependency graph: https://github.com/nodenv/devutil/network/dependents
It is listing a few other projects in the same org that have removed their dependency on the devutil project years ago. Why are those projects still being listed as Dependents? I realize that time is probably not the best metric; I assume git tags or the publishing of a GitHub Release is probably the trigger that causes the dependent rescan? Regardless, many of those dependents have had multiple commits to main, tags and releases since removing the devutil dependency. And yet still they show as devutil Dependents. What gives?
Beta Was this translation helpful? Give feedback.
All reactions