GitHub Release Watch – Breaking Changes Since Your Version
Pricing
from $2.00 / 1,000 repository checkeds
GitHub Release Watch – Breaking Changes Since Your Version
Schedule it daily for the repositories you depend on: new releases since your version, major bumps, and breaking-change lines pulled out of the release notes. Handles monorepo tags and backports correctly.
Pricing
from $2.00 / 1,000 repository checkeds
Rating
0.0
(0)
Developer
peti peti
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
a day ago
Last modified
Categories
Share
"Is it safe to upgrade?" – answered every morning for every library you depend on.
List the GitHub repositories you rely on, optionally with the version you use, and schedule this Actor daily. For each one you get:
- status:
up-to-date,update, orbreaking-update - how far behind you are (
releasesBehind) and whether the latest is a major upgrade - breaking-change lines pulled out of the release notes of every release since your version: "Breaking changes" sections plus lines like dropped support for Node 18,
legacyoption removed, 破壊的変更 - the new releases with links
Gets the tricky cases right
- Backports:
v6.4.5published afterv8.3.5is not "the latest" – versions are compared, not dates. - Monorepos: tags like
create-vite@9.3.1next tov8.3.5are kept apart; pick a package withowner/repo:package@version. - Drafts and pre-releases are skipped (pre-releases optional).
- Without
@version, each new release is reported once (remembered in a named key-value store), so a daily run is quiet when nothing happened.
Input
{"repositories": ["vitejs/vite@7.1.0", "nodejs/node", "vitejs/vite:create-vite@8.0.0"],"githubToken": "<optional, your own token>"}
A token is optional but recommended: without one GitHub allows 60 requests per hour per IP address, and cloud IPs are shared. A fine-grained token with no permissions is enough for public repositories.
Output (one row per repository line)
{"repository": "vitejs/vite","package": null,"status": "breaking-update","currentVersion": "7.1.0","latestVersion": "8.3.5","releasesBehind": 44,"majorUpgrade": true,"breakingNotes": ["8.0.0: drop Node 18", "8.3.4: remove input option unescaping for now (#23694)"],"latestUrl": "https://github.com/vitejs/vite/releases/tag/v8.3.5","newReleases": [{ "tag": "v8.3.5", "version": "8.3.5", "published": "2026-10-21T06:35:46Z", "majorBump": false, "breakingNotes": [] }]}
Breaking-change detection reads the release notes on GitHub. Projects that only write "see CHANGELOG.md" still get the major-version flag, but no extracted lines.
Fair use
Uses the official GitHub REST API – one request per repository – under GitHub's API terms. Only release data is read; no user profiles or personal information are collected (release authors are not included).
Pricing
Pay per event, platform usage included:
| Event | Price |
|---|---|
| Actor start | $0.01 per run |
repo-checked – one repository line checked | $2.00 per 1,000 ($0.002 each) |
Example: 20 dependencies checked daily ≈ 30 × ($0.01 + 20 × $0.002) = $1.50 per month. Errors (not found, rate limit) are free.
日本語での説明
使っているライブラリの GitHub リポジトリを毎日見張り、自分のバージョンより新しいリリース、メジャーアップデートかどうか、リリースノートから抜き出した「破壊的変更」の行を知らせます。古い版の修正リリース(バックポート)を「最新」と取り違えたり、モノレポの別パッケージのタグが混ざったりしないように、日付ではなくバージョン番号で比べます。公式の GitHub API を使い、個人情報は扱いません。
料金: 1回 $0.01 + 1リポジトリ $0.002。