GitHub Release Tracker

Problem It Solves

When maintaining multiple upstream dependencies or team repositories, releases and changelogs are scattered across GitHub. Manually reviewing them can miss breaking changes, security patches, or API changes that affect upgrades. github-release-tracker addresses this workflow: configure a list of GitHub projects, check updates automatically, and turn raw changes into summaries that make upgrade risk easier to evaluate.

How It Works

• Project configuration: maintain the tracking list in references/projects.json, or ask the agent to add a project such as xxx/yyy.
• Update checking: scripts/check_updates.py fetches the latest release and changelog, then returns structured JSON so downstream analysis does not depend on unstructured log text.
• Change analysis: classify updates into new features, bug fixes, breaking changes, documentation, performance, and security, then assess impact on existing functionality, migration steps, and upgrade strategy.
• Report output: save reports to the github-updates/ directory for archiving and review.
• Scheduled checks: configure recurring tasks for notification when updates appear or for a daily check.

Boundaries And Notes

It fits public GitHub project release and changelog tracking, but it is not a replacement for dependency pinning, dependency auditing, or full CI regression. If a project lacks a well-maintained changelog, analysis quality depends on release note completeness. For security updates, the report should be treated as an investigation entry point, not a final conclusion; verify the actual code, patch notes, and test environment before upgrading.