I'm curious about how developers manage the obsolescence of their packages, such as programming languages, frameworks, and Docker images. I know that tools like Renovate are helpful for this through continuous integration, but I'm specifically looking for strategies to track which packages are becoming obsolete, approaching end-of-life, or still in good shape. Ideally, I'm looking for a dashboard-style solution. How do you all handle this?
3 Answers
If your codebase is large, you might want to have someone dedicated to this task. Keeping track of everything can be a lot, and having a dedicated developer can help ensure that packages are maintained without slipping through the cracks.
For open source packages, we've found it useful to track dependencies through their GitHub repositories. By utilizing the GitHub API along with some other tools, we can generate reports on the health of these projects regularly and act accordingly. Once it's set up, it works really well!
One effective way to manage package versions is to use a Software Bill of Materials (SBOM). There are various tools available that help track version histories of your packages. It provides a clear overview of what needs updating or replacing.
Related Questions
How To: Running Codex CLI on Windows with Azure OpenAI
Set Wordpress Featured Image Using Javascript
How To Fix PHP Random Being The Same
Why no WebP Support with Wordpress
Replace Wordpress Cron With Linux Cron
Customize Yoast Canonical URL Programmatically