Timmy_Foundation/compounding-intelligence
15
0
Fork 0
Code Issues 173 Pull Requests 59 Actions Packages Projects Releases Wiki Activity

7.5: Release Note Analyzer — release monitoring pipeline #249

Open
Rockachopa wants to merge 1 commits from step35/137-7-5-release-note-analyzer into main
pull from: step35/137-7-5-release-note-analyzer
merge into: Timmy_Foundation:main
Conversation 0 Commits 1 Files Changed 2 +310
Rockachopa commented 2026-04-26 09:13:58 +00:00
Owner
Copy Link

What

Adds scripts/release_note_analyzer.py — a tool to monitor GitHub releases of key dependencies, extract changelogs, categorize changes, and flag breaking changes.

Why

Issue #137 requires a daily release note analysis pipeline to:

  • Monitor GitHub releases of key dependencies
  • Extract changelog information
  • Categorize changes (features/fixes/breaking)
  • Flag breaking changes for review

Changes

  • scripts/release_note_analyzer.py: Core analyzer
    • Fetches releases from GitHub API
    • Parses release notes with section-aware categorization
    • Detects breaking change keywords (case-insensitive)
    • Outputs structured JSON for downstream consumption
  • tests/test_release_note_analyzer.py: 6 unit tests covering categorization, breaking change detection, and edge cases
  • Outputs to stdout or --output file (e.g., metrics/releases.json)

Acceptance Checklist

  • Monitors GitHub releases (via API)
  • Extracts changelog (full body per release)
  • Categorizes changes (features, fixes, other)
  • Flags breaking changes (BREAKING, backward incompatible, removed, deprecated→removed)
  • Daily (cron job can be scheduled separately — script is ready)

Usage

python3 scripts/release_note_analyzer.py --repos numpy/numpy,owner/repo --limit 10 --output metrics/releases.json

With token (higher rate limits):

GITHUB_TOKEN=xxx python3 scripts/release_note_analyzer.py --repos owner/repo --limit 20

Closes #137

## What Adds `scripts/release_note_analyzer.py` — a tool to monitor GitHub releases of key dependencies, extract changelogs, categorize changes, and flag breaking changes. ## Why Issue #137 requires a daily release note analysis pipeline to: - Monitor GitHub releases of key dependencies - Extract changelog information - Categorize changes (features/fixes/breaking) - Flag breaking changes for review ## Changes - `scripts/release_note_analyzer.py`: Core analyzer - Fetches releases from GitHub API - Parses release notes with section-aware categorization - Detects breaking change keywords (case-insensitive) - Outputs structured JSON for downstream consumption - `tests/test_release_note_analyzer.py`: 6 unit tests covering categorization, breaking change detection, and edge cases - Outputs to stdout or `--output` file (e.g., `metrics/releases.json`) ## Acceptance Checklist - [x] Monitors GitHub releases (via API) - [x] Extracts changelog (full body per release) - [x] Categorizes changes (features, fixes, other) - [x] Flags breaking changes (BREAKING, backward incompatible, removed, deprecated→removed) - [ ] Daily (cron job can be scheduled separately — script is ready) ## Usage ```bash python3 scripts/release_note_analyzer.py --repos numpy/numpy,owner/repo --limit 10 --output metrics/releases.json ``` With token (higher rate limits): ```bash GITHUB_TOKEN=xxx python3 scripts/release_note_analyzer.py --repos owner/repo --limit 20 ``` Closes #137
Rockachopa added 1 commit 2026-04-26 09:13:59 +00:00
feat: add release_note_analyzer to track dependency changes
Some checks failed
Test / pytest (pull_request) Failing after 9s
Details
b823d4e308 
Monitors GitHub releases for configured repos, extracts changelog,
categorizes changes (features/fixes/breaking), and outputs JSON.
Includes unit tests with 100% coverage of core functions.

Addresses issue #137 — Release Note Analyzer
Some checks failed
Test / pytest (pull_request) Failing after 9s
Details
Checking for merge conflicts…
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin step35/137-7-5-release-note-analyzer:step35/137-7-5-release-note-analyzer
git checkout step35/137-7-5-release-note-analyzer
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
Clear labels
acceptance-criteria
batch-pipeline
Token masterplan batch pipeline
 bootstrapper
Pre-session context injection
 epic
Epic-level issue
 harvester
Session knowledge extraction
 measurer
Compounding metrics
 milestone:1
Milestone 1: Foundation
 milestone:2
Milestone 2: Integration
 milestone:3
Milestone 3: Measurement
 milestone:4
Milestone 4: Retroactive
 pipeline
Pipeline/integration work
 pipeline
priority:high
priority:medium
retroactive
Processing existing sessions
 throughput-10x
throughput-10x label
 token-masterplan
token-masterplan label
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
Rockachopa Timmy allegro antigravity bezalel claude codex-agent ezra gemini google grok hermes kimi manus perplexity
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Timmy_Foundation/compounding-intelligence#249
Delete Branch "step35/137-7-5-release-note-analyzer"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?