Release Tracker

Monitor one or more GitHub repositories for new releases, generate prioritized summaries, and deliver them to configured channels.

Prerequisites

• - gh CLI installed and authenticated (gh auth status)
• For Discord delivery: Discord channel configured in OpenClaw

Quick Start

Single Repo Setup

Set up tracking for one repo with a cron job:

CODEBLOCK0

Multi-Repo Setup

Add multiple repos to the repos array in config. Each repo has independent version tracking and priority rules.

Configuration

Store config at <workspace>/release-tracker.json:

CODEBLOCK1

Config Fields

• - repos[].owner / repos[].repo — GitHub owner/repo
• INLINECODE6 — friendly name for output header
• INLINECODE7 — keywords to sort higher in summary (matched against changelog text)
• INLINECODE8 — Discord channel/forum ID for delivery
• INLINECODE9 — discord-forum | discord-channel | telegram | slack | INLINECODE14

• - repos[].language — zh | en (summary language)
• INLINECODE23 — track pre-release/RC versions
• INLINECODE24 — optional, stable | all (default: stable)
• INLINECODE28 — filename for tracking last-seen versions (relative to workspace)
• INLINECODE29 — cron expression for check frequency
• INLINECODE30 — timezone for cron schedule

Workflow

Check for New Releases

1. 1. Read config from INLINECODE31
2. Read version state from INLINECODE32
3. For each repo:

   gh release list --repo <owner>/<repo> --limit 5 --json tagName,publishedAt,isPrerelease
   

1. 4. Compare latest tag against stored version
2. If new version found, proceed to summarize

Generate Summary

1. 1. Fetch release content:

   gh release view <tag> --repo <owner>/<repo> --json body
   

1. 2. If release body is sparse, also check local CHANGELOG if the package is installed:

   cat /opt/homebrew/lib/node_modules/<package>/CHANGELOG.md
   

1. 3. Parse and categorize changes into sections:

Prioritization Rules

Sort entries within each section:

1. 1. Lines matching priorities keywords → top
2. User-facing changes → middle
3. Internal/infrastructure → bottom
4. Omit: trivial fixes, test-only changes, doc typos

Format Output

Discord Forum (discord-forum)

CODEBLOCK5

Discord Channel (discord-channel)

Compact single-message format, max 2000 chars.

Telegram (telegram)

Same structure as Discord Channel but respects Telegram formatting (markdown v2). Max 4096 chars.

Slack (slack)

Same structure, uses Slack mrkdwn formatting. Max 3000 chars.

Text (text)

Plain markdown, no emoji headers.

Deliver

Based on outputFormat:

• - discord-forum: INLINECODE42
• INLINECODE43: INLINECODE44
• INLINECODE45: INLINECODE46
• INLINECODE47: INLINECODE48
• INLINECODE49: return as tool result

Update State

After successful delivery, update version store:
CODEBLOCK6

Cron Setup

Create the cron job for automated checking:

CODEBLOCK7

The cron message should instruct the agent to:

1. 1. Read release-tracker.json for config
2. Read release-tracker-state.json for last versions
3. Check each repo via INLINECODE52
4. If new releases found, generate summaries and deliver
5. Update state file

Manual Check

User can trigger manually: "check for new releases" or "any updates on openclaw?"

The agent should:

1. 1. Load config
2. Run the check workflow
3. Report findings conversationally (not necessarily in forum format)