Files

T

Alex Newman ecb8b39f6d Add auto-generated CHANGELOG from GitHub releases

New Features:
- Created scripts/generate-changelog.js to auto-generate CHANGELOG.md
- Fetches all GitHub releases and formats into Keep a Changelog format
- Added npm run changelog:generate command

Version-Bump Skill Updates:
- Added Step 10: Generate CHANGELOG to workflow
- Updated verification checklist to include CHANGELOG generation
- Updated skill description and critical rules
- Single source of truth: GitHub releases

Technical Details:
- Script fetches releases via gh CLI
- Parses release bodies and formats to markdown
- Removes duplicate headers and Claude Code footers
- Sorts releases by date (newest first)
- Generates clean, consistent changelog

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>

2025-11-11 16:26:10 -05:00

3.0 KiB

Raw Blame History

name, description

name	description
version-bump	Manage semantic version updates for claude-mem project. Handles patch, minor, and major version increments following semantic versioning. Updates package.json, marketplace.json, plugin.json, and CLAUDE.md version number (NOT version history). Creates git tags and GitHub releases. Auto-generates CHANGELOG.md from releases.

Version Bump Skill

Manage semantic versioning across the claude-mem project with consistent updates to all version-tracked files.

Quick Reference

Files requiring updates (ALL FOUR):

package.json (line 3)
.claude-plugin/marketplace.json (line 13)
plugin/.claude-plugin/plugin.json (line 3)
CLAUDE.md (line 9 ONLY - version number, NOT version history)

Semantic versioning:

PATCH (x.y.Z): Bugfixes only
MINOR (x.Y.0): New features, backward compatible
MAJOR (X.0.0): Breaking changes

Quick Decision Guide

What changed?

"Fixed a bug" → PATCH (5.3.0 → 5.3.1)
"Added new feature" → MINOR (5.3.0 → 5.4.0)
"Breaking change" → MAJOR (5.3.0 → 6.0.0)

If unclear, ASK THE USER explicitly.

Standard Workflow

See operations/workflow.md for detailed step-by-step process.

Quick version:

Determine version type (PATCH/MINOR/MAJOR)
Calculate new version from current
Preview changes to user
Update ALL FOUR files
Verify consistency
Build and test
Commit and create git tag
Push and create GitHub release
Generate CHANGELOG.md from releases and commit

Common Scenarios

See operations/scenarios.md for examples:

Bug fix releases
New feature releases
Breaking change releases

Critical Rules

ALWAYS:

Update ALL FOUR files with matching version numbers
Create git tag with format vX.Y.Z
Create GitHub release from the tag
Generate CHANGELOG.md from releases after creating release
Ask user if version type is unclear

NEVER:

Update only one, two, or three files
Skip the verification step
Forget to create git tag or GitHub release
Add version history entries to CLAUDE.md (that's managed separately)

Verification Checklist

Before considering the task complete:

All FOUR files have matching version numbers
npm run build succeeds
Git commit created with all version files
Git tag created (format: vX.Y.Z)
Commit and tags pushed to remote
GitHub release created from the tag
CHANGELOG.md generated and committed
CLAUDE.md: ONLY line 9 updated (version number), NOT version history

Reference Commands

# View current version
grep '"version"' package.json

# Verify consistency across all version files
grep '"version"' package.json .claude-plugin/marketplace.json plugin/.claude-plugin/plugin.json

# View git tags
git tag -l -n1

# Check what will be committed
git status
git diff package.json .claude-plugin/marketplace.json plugin/.claude-plugin/plugin.json CLAUDE.md

For more commands, see operations/reference.md.

3.0 KiB Raw Blame History