chore(release): standardized release-notes renderer + auto GitHub Release - #70
Merged
Conversation
…ease Adds pipeline/render_release_notes.py, which renders a consistent Markdown body for a release (version + skill count + delta + per-source breakdown + the current install instructions: Claude Code /plugin, npx skills, finish-setup) from data/version.txt + data/release_log.jsonl. npm-publish.yml now creates a GitHub Release for each published tag using this renderer, so every future release on the Releases page has the same structure (previously the auto-publish only pushed a bare tag with no notes). Tests cover version/count/delta, sources, current install commands, custom + default highlights, and the first-release case. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Standardizes the GitHub Releases page.
Problem: release notes were inconsistent (each
v*used a different structure with outdatedcpinstall commands), andv0.1.2had no GitHub Release at all (the auto-publish workflow only pushed a bare tag).Fix:
pipeline/render_release_notes.pyrenders a consistent body fromdata/version.txt+data/release_log.jsonl: version + skill count + delta + per-source breakdown + the current install instructions (Claude Code/plugin,npx skills, finish-setup).npm-publish.ymlnow creates a GitHub Release per published tag using the renderer — so every future release is structured identically.Separately (GitHub-side, not in this PR): I'm creating the missing
v0.1.2release and re-standardizingv0.1.0/v0.1.1to the same format, and improved the repo description/topics/homepage.Verification: 585 tests pass (6 new); ruff clean; workflow YAML parses; renderer output validated against the live data.
🤖 Generated with Claude Code