Changelog Monitor: Competitor Release Notes & GitHub Releases avatar

Changelog Monitor: Competitor Release Notes & GitHub Releases

Pricing

from $2.80 / 1,000 changelog entries

Go to Apify Store
Changelog Monitor: Competitor Release Notes & GitHub Releases

Changelog Monitor: Competitor Release Notes & GitHub Releases

Track release notes and changelogs for any product: GitHub releases, RSS and Atom changelog feeds, or plain changelog pages. Version, title, date, summary and link per entry, with a new-only mode for monitoring. No login, no key, no proxy.

Pricing

from $2.80 / 1,000 changelog entries

Rating

0.0

(0)

Developer

Detroit Web Agent - Open Data

Detroit Web Agent - Open Data

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

a day ago

Last modified

Features

Limited permissions

Share

Changelog monitor for any product: pull release notes from GitHub releases, RSS and Atom changelog feeds and plain changelog pages into one flat table with version, title, date, summary and link. Switch on new-only mode and schedule it to get a feed of fresh releases. No login, no key, no proxy.

Know what your competitors and your own dependencies shipped this week. Give the Actor a list of products and it returns their latest release notes in one clean, comparable format, ready for a spreadsheet, a Slack alert, a CRM note or an AI agent.

What is Changelog Monitor?

Changelog Monitor reads public release information and nothing else. For a GitHub repo it reads the public releases feed. For a feed URL it reads the RSS or Atom entries. For a changelog page it looks for the page's own feed link first, and if there is none it reads the version and date headings on the page. Every entry becomes one row: product, version, title, publication time, a plain-text summary of the notes, a link, and a pre-release flag. Run it from the Apify Console, the API, a schedule, n8n, Make, Zapier or an MCP client.

Why use it

  • Three source types in one run. GitHub repos, feed URLs and changelog pages, mixed freely in the same list.
  • Monitoring mode. With Only entries I have not seen on, the first run returns the latest entries and every later run returns only what was published since.
  • Comparable rows. The same fields for every product, so you can sort by date across all competitors.
  • Pre-release control. Drop alpha, beta, rc, canary and nightly builds with one switch.
  • No setup. No GitHub token, no API key, no proxy, no browser.
  • Pay for rows only. Filter first, then pay for the rows you receive. No monthly fee.

Output

One row per release or changelog entry:

FieldMeaning
sourceThe product exactly as you entered it.
sourceTypegithub, feed or page.
productRepository name, feed title or site name.
versionVersion or tag, for example v15.0.1 (empty when the entry carries none).
titleRelease or entry title.
publishedAtPublication time as ISO 8601 (empty when the source gives no date).
summaryFirst 500 characters of the release notes as plain text.
urlLink to the release or changelog entry.
isPrereleaseTrue for alpha, beta, rc, canary, nightly and preview builds.
wordCountWords in the full release notes, a quick size signal for ranking changes.
scrapedAtWhen the run read the data.

Sample output

{
"source": "vercel/next.js",
"sourceType": "github",
"product": "next.js",
"version": "v16.4.6",
"title": "v16.4.6",
"publishedAt": "2026-11-09T20:27:17.000Z",
"summary": "This release is backporting bug fixes. Core Changes ...",
"url": "https://github.com/vercel/next.js/releases/tag/v16.4.6",
"isPrerelease": false,
"wordCount": 120,
"scrapedAt": "2026-11-10T12:00:00.000Z"
}

Input

FieldWhat it does
sourcesProducts to track, one per line: a GitHub repo (vercel/next.js or the repo URL), a feed URL, or a changelog page URL.
maxPerSourceNewest entries to return per product. Default 5.
onlyNewReturn only entries not seen in an earlier run. Default off.
sinceDaysSkip entries older than this many days. 0 means no filter.
includePrereleasesTurn off to drop alpha, beta, rc, canary and nightly builds. Default on.
maxItemsStop after this many rows in total. Default 100.

Sample input:

{
"sources": ["vercel/next.js", "n8n-io/n8n", "https://stripe.com/blog/changelog"],
"maxPerSource": 5,
"onlyNew": true,
"sinceDays": 30
}

Pricing

Pay per event, no subscription. Current prices:

EventPrice
Actor Start$0.00005
Changelog entry$0.0028

Apify's free plan includes monthly platform credit that covers test runs.

A scheduled price change is on file and takes effect on its start date. The Pricing tab always shows current and upcoming prices.

Examples at the current price (one changelog-entry event per result; Free-plan tier):

You pullYou pay
100 results$0.28
1,000 results$2.80
10,000 results$28.00

Scheduled runs stay cheap when each run only returns new records.

What does this Actor do?

For every source it makes one to two plain HTTP requests. GitHub repos use the public releases feed (and the tags feed for repos that never published a release). Feed URLs are parsed directly. For a page URL the Actor reads the page, follows the feed it advertises if there is one, and otherwise reads headings that contain a version number or a date. Entries are converted to flat rows, filtered by your date and pre-release settings, and charged one per row. If a source cannot be read, the run continues with the others and the reason is listed in the OUTPUT record of the key-value store.

Run in 30 seconds

  1. Open the Actor and press Try for free (a free Apify account is enough).
  2. Keep the prefilled list of products, or replace it with your own, and press Start.
  3. Open the Output tab. Use the table view or download CSV, Excel or JSON.

Use cases

  • Product and competitive teams: a weekly digest of what every competitor shipped, sorted by date.
  • Engineering teams: watch the releases of the libraries and tools you depend on and get alerted to new versions.
  • Customer success and support: know when a vendor you integrate with changed something.
  • Agencies and consultants: keep client stacks current and flag upgrades worth selling.
  • Investors and analysts: track shipping cadence of portfolio or target companies as a leading signal.
  • AI agents: give an agent a tool that answers "what changed in product X lately?" with structured rows.

Limits

  • GitHub release feeds hold the latest 10 entries, so older history is not available through them.
  • Changelog pages without a feed are read by their headings; unusual layouts may return fewer entries or none. A feed URL is more reliable when the product offers one.
  • Pages that need a login or build their content only in the browser are not supported.
  • version and publishedAt stay empty when the source does not provide them; the Actor does not guess.
  • Up to 5,000 rows per run.

Found a bug or need a field? Open an issue on the Issues tab with the run URL.

Use with the API, n8n, Make, Zapier or AI agents

API (one call, returns the rows as JSON):

curl -X POST "https://api.apify.com/v2/acts/transparent_meteorite~changelog-monitor/run-sync-get-dataset-items?token=YOUR_APIFY_TOKEN" \
-H "Content-Type: application/json" \
-d '{"sources": ["vercel/next.js", "n8n-io/n8n"], "maxPerSource": 5}'

The call waits up to 5 minutes. For bigger inputs, start the run with /runs instead and read the dataset when it finishes.

Python

from apify_client import ApifyClient
client = ApifyClient("YOUR_APIFY_TOKEN")
run = client.actor("transparent_meteorite/changelog-monitor").call(run_input={"sources": ["vercel/next.js", "n8n-io/n8n"], "maxPerSource": 5})
for row in client.dataset(run["defaultDatasetId"]).iterate_items():
print(row)

MCP (AI agents): connect the Apify MCP server at https://mcp.apify.com?tools=transparent_meteorite/changelog-monitor to Claude, Cursor or any MCP client. Your agent can then check competitor release notes, see what changed in a dependency and list new versions by calling this Actor, and it gets back the same flat rows described above.

ToolSetup
n8nAdd the Apify node, choose "Run Actor", set the actor to transparent_meteorite/changelog-monitor, paste the input JSON with onlyNew on, then add a "Get Dataset Items" step and send each row to Slack, email or your sheet.
Make and ZapierUse the Apify app's "Run Actor" action with this actor and the input JSON, then map the dataset items.
ClayAdd an HTTP API column that calls the run-sync endpoint above.
SchedulesIn Apify Console, Schedules, run it daily with onlyNew on for a feed of fresh releases only.

Search terms people use

changelog monitor, release notes tracker, competitor release notes, GitHub releases scraper, track software releases, product changelog tracker, new version alerts, release feed to JSON, SaaS changelog monitoring, what's new tracker.

FAQ

Which sources work best? GitHub repos and feed URLs are the most reliable. Many products publish a feed at /changelog.xml, /feed or /releases.atom; paste that URL. For other changelog pages the Actor tries the page's own feed link and then its headings.

How does monitoring work? Turn on Only entries I have not seen and schedule the run. The first run returns the latest entries and remembers them in your account; later runs return only entries published after that.

Do I need a GitHub token? No. The Actor reads the public releases feed, which has no key and does not count against the REST API limit.

Why is version empty for some rows? Some changelogs name entries by date or feature instead of a version number. The field stays empty rather than guessed.

Can it read private repositories? No. It only reads public information.

More from DWA Open Data

Browse all our data Actors, with live prices and sample output, at open-data-actors.pages.dev.


Feedback: if this Actor was useful, or if it fell short, an honest review on the Reviews tab helps other users decide. Problems or feature requests: please open an Issue and we usually reply within one business day.