GitHub Release Notes: Changelog Between Versions

What does GitHub Release Notes: Changelog Between Versions do?

GitHub Release Notes reads a GitHub repository's own release notes, newest first, and can give you only what changed since the version you run today.

Give it repositories like facebook/react or a github.com link. For each one you get its latest stable version and every release with its version tag, name, publish date, full release notes and link. Add sinceVersion (say 18.2.0) and the row holds just the releases you would cross by upgrading.

You pay one flat price per repository, not per release, so 100 releases cost the same as 1.

It never signs in anywhere and never changes anything. It only reads public repositories.

Why use it?

• Planning an upgrade. "We are on Next.js 15.3, what changed since?" One row with every release note in between, ready to read or hand to a model for breaking changes.
• Watching dependencies. Run your list of repositories on a schedule and see each one's latest version and date in one table.
• AI agents. Connect it as an MCP server and let an agent answer "what is new in React since 19.0?" while it works.

How it works

For each repository:

1. It reads the repository's published releases on GitHub, up to the 100 most recent.
2. It drops drafts, and prereleases (canary, beta, release candidates) unless you ask for them.
3. With sinceVersion, it keeps only releases that are newer than that version both in date and in version number, so an older line's patch release published later does not show up in your upgrade.

Input

Field	Required	Description
repos	Yes	One repository per entry: "owner/repo" or any github.com link inside it.
sinceVersion	No	The version you run today, like "18.2.0" or "v14.2.3". Only newer releases come back.
maxReleases	No	At most this many releases per repository, 1 to 100. Default 20.
includePrereleases	No	Also list canary, beta and release candidate versions. Default false.
maxConcurrency	No	Repositories processed at once, 1 to 8. Default 4.

Example input:

{ "repos": ["facebook/react", "https://github.com/vercel/next.js"], "sinceVersion": "19.2.0" }

Output

One dataset row per repository, with every matching release in the releases column. Download it as JSON, CSV, Excel or HTML, or read it through the Apify API.

{
  "input": "facebook/react",
  "sinceVersion": "v19.2.0",
  "status": "found",
  "repo": "facebook/react",
  "latestVersion": "v19.3.1",
  "latestPublishedAt": "2026-10-14T17:06:15Z",
  "releaseCount": 11,
  "releases": [
    {
      "version": "v19.3.1",
      "name": "19.3.1 (October 14th, 2026)",
      "prerelease": false,
      "publishedAt": "2026-10-14T17:06:15Z",
      "notes": "## React Server Components\r\n\r\n- Improve transport protocol ([#37845](https://github.com/facebook/react/pull/37845) by @unstubbable and @eps1lon)",
      "url": "https://github.com/react/react/releases/tag/v19.3.1"
    }
  ],
  "warnings": [],
  "error": null
}

status is found, not_found or error. not_found means the repository was read and has no releases matching your filters, or publishes no GitHub releases at all (some projects only push tags); that is a real answer and warnings says which. error means GitHub has no public repository by that name.

Pricing

$0.006 per repository, with no monthly fee, however many releases it returns.

• A repository is charged when its release history is read, even if no release matches your filters.
• A repository that does not exist, or that fails with an error, is not charged.
• Set a spending limit on the run and the Actor stops cleanly when it reaches it.
• On Apify's free plan, each run processes the first 10 repositories (10 tool calls per MCP session). Any paid Apify plan removes the limit.

Use it as an MCP server

This Actor also runs as an MCP server with one tool, get_release_notes. Point any MCP client (Claude, Cursor, ChatGPT, your own agent) at:

https://bowmark-ai--github-release-notes.apify.actor/mcp

with your Apify API token as a bearer token. Each tool call is billed like one repository in a normal run.

Limits and good practice

• It reads only public repositories. It never signs in anywhere and never changes anything.
• It reads the 100 most recent releases. For a project that ships many canaries a day, sinceVersion far in the past may reach back only that far; the row warns you when it does.
• Release notes come from the project's GitHub Releases page. A project that keeps its changelog only in a file in the repository (Go, for one) has no releases to read and comes back not_found.
• Notes longer than 20,000 characters are cut, with the link to the full release.

Questions or a wrong result?

Open an issue on the Issues tab with the input you used and what you expected. We read every one.