Next.js releases
Input URL
https://github.com/vercel/next.js/releasesExpected feed
https://github.com/vercel/next.js/releases.atomTest in finderRSS by platform
GitHub exposes Atom feeds for releases, commits, tags, and personal activity.
Quick answer
https://github.com/[owner]/[repo]/releases.atomContext
GitHub has exposed Atom feeds for almost every page type since the mid-2010s as a technical-user convenience. Feeds are Atom (not RSS), and the URL pattern adds .atom to an existing page path. Feeds are public for public repositories and require authentication for private ones, which most RSS aggregators cannot provide.
https://github.com/[owner]/[repo]/releases.atomhttps://github.com/vercel/next.js/releases.atomRSS finder
Test a GitHub URL here to get the same feed analysis, import verdict, and live Aggregator-style preview as the main Feed Finder.
Gotchas
Examples
Input URL
https://github.com/vercel/next.js/releasesExpected feed
https://github.com/vercel/next.js/releases.atomTest in finderInput URL
https://github.com/vercel/next.js/commits/canaryExpected feed
https://github.com/vercel/next.js/commits/canary.atomTest in finderInput URL
https://github.com/vercel/next.js/tagsExpected feed
https://github.com/vercel/next.js/tags.atomTest in finderInput URL
https://github.com/torvaldsExpected feed
https://github.com/torvalds.atomTest in finderGet this into WordPress
Once you have a working GitHub feed URL, Aggregator handles the rest, importing as posts, rendering as a display, or filtering before it publishes.
Grab the URL from the finder above or the examples list.
Paste into Add New Feed Source inside WordPress.
Render as a list, import as posts, or filter by keyword before anything goes live.
FAQ
GitHub exposes Atom feeds (not RSS 2.0) for releases, commits, tags, and user activity. Atom and RSS are both readable by Aggregator. Most tools treat them interchangeably.
Use https://github.com/[owner]/[repo]/releases.atom. This returns the most recent published releases for the repository. Draft releases are not exposed in the Atom feed.
Not directly. GitHub does not expose Atom feeds for issues or pull requests. Use the REST API or GraphQL API, or third-party bridges, if you need those.
Use https://github.com/[owner]/[repo]/commits/[branch].atom. Replace [branch] with the branch name, for example main or master.
They expose the same .atom URLs, but those URLs require authentication. Most public RSS aggregators cannot access them without a token.
Yes. Use https://github.com/[username].atom to get a feed of that user's public events: pushes, releases, repository creations, fork activity. It is noisier than a release feed and best paired with keyword or repository filtering at import time.