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:

1. Create a config file at <workspace>/release-tracker.json (see Configuration)
2. Create a cron job (isolated, daily) that runs the check
3. The cron reads config, checks GitHub, compares versions, posts if new

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 /release-tracker.json:

{
  "repos": [
    {
      "owner": "openclaw",
      "repo": "openclaw",
      "displayName": "OpenClaw",
      "priorities": ["discord", "voice", "telegram", "cron", "agent"],
      "outputChannel": "<your-discord-channel-id>",
      "outputFormat": "discord-forum",
      "language": "en",
      "includePrerelease": false
    }
  ],
  "versionStore": "release-tracker-state.json",
  "schedule": "0 10 * * *",
  "timezone": "UTC"
}

Config Fields

• repos[].owner / repos[].repo — GitHub owner/repo
• repos[].displayName — friendly name for output header
• repos[].priorities — keywords to sort higher in summary (matched against changelog text)
• repos[].outputChannel — Discord channel/forum ID for delivery
• repos[].outputFormat — discord-forum | discord-channel | telegram | slack | text
• discord-forum: create a new forum post per release
• discord-channel: send a message to a Discord channel
• telegram: send a message to a Telegram chat/channel/group
• slack: send a message to a Slack channel
• text: return plain text (for piping to other tools)
• repos[].language — zh | en (summary language)
• repos[].includePrerelease — track pre-release/RC versions
• repos[].filter — optional, stable | all (default: stable)
• versionStore — filename for tracking last-seen versions (relative to workspace)
• schedule — cron expression for check frequency
• timezone — timezone for cron schedule

Workflow

Check for New Releases

• Read config from release-tracker.json
• Read version state from
• For each repo:

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

• Compare latest tag against stored version
• If new version found, proceed to summarize

Generate Summary

• Fetch release content:

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

• If release body is sparse, also check local CHANGELOG if the package is installed:

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

• Parse and categorize changes into sections:
• Priority items — lines matching any priorities keywords, shown first
• Features — new capabilities
• Breaking changes — marked with ⚠️
• Fixes — bug fixes relevant to user (skip internal/CI fixes)
• Security — collapsed at bottom unless critical
• Skip: CI/test-only changes, dependency bumps, internal refactors

Prioritization Rules

Sort entries within each section:

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

Format Output

#### Discord Forum (discord-forum)

Title: 📦 v{version}

Body:
## {displayName} v{version}

### ⭐ Key Features
{priority matches + features, formatted as bold headers with descriptions}

### ⚠️ Breaking Changes
{breaking changes with migration notes}

### 🔧 Fixes
{relevant fixes, grouped by area}

### 🛡️ Security
{security fixes, brief}

#### 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: message(action=thread-create, channelId=, threadName=