Skip to content

How to Monitor an Open-Source Project: Releases, Changelog and Discussions

The places an open-source project announces change, GitHub's own release notifications and Atom feeds, and when a filtered summary of breaking changes is worth adding.

By AyeWatch Team4 min read

Short answer: Start with GitHub: a repository's Custom notification setting can send only new releases, and every repo publishes a releases Atom feed at /releases.atom. For a summary that calls out breaking changes, add AyeWatch web page monitors on the releases page and the Discussions announcements page, plus an X or Reddit search for the project's name.

Where a project announces change

  • Releases page at github.com/owner/repo/releases. On 21 November 2026 Vite's page showed v8.3.8 marked Latest, released on 11 November, with notes grouped under Bug Fixes and Performance Improvements, and a v8.4.0-beta.1 pre-release from 16 November.
  • Changelog file, usually CHANGELOG.md. Long-lived projects have very long ones; Vite's changelog page was over 2 MB of HTML.
  • Discussions, often with an Announcements category at /discussions/categories/announcements, for roadmaps, deprecations and calls for feedback.
  • Security advisories at /security/advisories, public for published advisories.
  • The project's own site or blog, where major versions get a migration guide.

The GitHub pages on this list loaded without signing in when we checked Vite's.

GitHub's own options come first

Release notifications. GitHub's docs say the repository's "Watch" menu has a Custom option where you pick event types: issues, pull requests, releases, security alerts and discussions. Pick only Releases. Notifications go to your GitHub inbox on the web, GitHub Mobile and email. You need a GitHub account.

Atom feeds. Add /releases.atom or /tags.atom to the repository address. Both returned feeds for Vite on 21 November 2026, newest first. Any feed reader works.

Both send everything: every patch release, every pre-release, every tag. For a project you follow closely, that is fine. For twenty dependencies, it is a pile of notifications that say "v2.14.3" and little else.

Where a monitor adds something

A web page monitor on the releases page reads the notes and applies your rule. That is useful when the question is "does this release affect me?" rather than "was there a release?".

Sample rule. "Alert me on new stable releases of lumen-orm. Skip pre-releases, betas and nightly tags. Summarize breaking changes, deprecations and security fixes. If there are none, say so in one line."

Sample alert. The headline reads "lumen-orm v4.0.0: two breaking changes." The summary says the release drops support for Node 18, renames the findMany option where to filter, deprecates the old migration CLI, and fixes one SQL injection issue in raw queries. It links to the release. lumen-orm is an invented project.

Point a second monitor at the Announcements discussions with a rule for deprecations and roadmap posts. Those usually come before the breaking release.

The changelog and the size problem

AyeWatch reads a page up to a size limit, so a very long changelog may be read in part. The releases page shows the newest releases first, which is what a monitor needs. If a project only keeps a changelog file, monitor it and check that the first result includes the newest entries. If it doesn't, monitor the project's docs page for the current version instead.

What people say about the project

Release notes say what changed. Users say what broke. An X search for the project's name plus "broke" or "upgrade" (2 credits a check) and a search in subreddit for the language or framework subreddit (1 credit) catch upgrade reports. A YouTube search finds conference talks and migration walkthroughs. For licensing changes, read monitor open-source license changes.

Pace and cost

Daily checks are enough for most projects. Releases page, announcements and an X search, all daily, use 120 credits a month per project, so Pro's 500 credits cover four projects. For a dependency with security exposure, check its releases and advisories pages twice a day. AyeWatch Pro is $9/mo with 50 topics and hourly checks; Pro+ is $19/mo with 200 topics and ASAP mode. Every plan starts with a 7-day free trial. Paid plans send alerts to Slack or a signed webhook, so release summaries can land in an engineering channel.

When AyeWatch is the wrong tool

For every commit, issue and pull request, use GitHub notifications. To open upgrade pull requests automatically, a dependency bot in your repository does the job. Private repositories need a login, so a page monitor can't read them. For package registries rather than GitHub, see npm package update alerts, and the changelog monitor page covers product changelogs outside GitHub.

SourceWhereGitHub's free optionAyeWatch
Releases/releasesCustom notifications: Releases; /releases.atomPage monitor with a breaking-change rule
Tags/tags/tags.atomRarely needed
Changelog fileCHANGELOG.mdNonePage monitor; check the first result on long files
Announcements/discussions/categories/announcementsCustom notifications: DiscussionsPage monitor for deprecations and roadmaps
Security advisories/security/advisoriesCustom notifications: Security alertsPage monitor, twice a day
User reportsX, RedditNoneX Search, Search in subreddit

Start a monitor in under a minute

Describe a topic or paste a URL. Cancel before the trial ends and you pay nothing.

Try it free for 7 days

The bottom line

Turn on GitHub's release-only notifications for the projects you follow closely. For the dependencies where a breaking change would cost you a day, add a releases page monitor with a rule that names breaking changes and security fixes.

FAQ

How do I get notified only when a GitHub repo publishes a release?

Open the repository's notification menu, choose Custom and select Releases. GitHub sends those notifications to the web inbox, GitHub Mobile and email.

Does every GitHub repository have a releases feed?

Yes. Add /releases.atom to the repository address. Tags have a feed at /tags.atom.

Can AyeWatch skip pre-releases and summarize breaking changes?

Yes. Put a web page monitor on the releases page and write that in the rule.

Can AyeWatch monitor a private repository?

No. It reads public pages only, and private repositories need a login.

How many open-source projects can I monitor on Pro?

A releases page, an announcements page and an X search per project, all daily, use about 120 credits a month, so Pro's 500 credits cover four projects.

how to monitor an open source projectgithub release notificationsgithub releases atom feedtrack open source project updatesopen source breaking change alerts

Related articles