A specialized CLI tool (@runespoor/changelog-manager) designed for managing changelogs and semantic versioning in single repositories, particularly optimized for Continuous Integration and Trunk Based Development workflows.
Key Features: Automated Version Management - intelligently handles semantic versioning based on change types. Standardized Change Documentation - enforces consistent changelog formats. CI/CD Integration - built-in commands for verification in CI pipelines. Issue Tracking - optional integration with issue tracking systems. Git Integration - automated commit and push functionality.
Use Cases: Maintaining consistent changelog entries across team members. Automating version bumps based on change significance. Enforcing change documentation in CI/CD pipelines. Tracking changes with associated issue references. Standardizing release documentation
The tool essentially automates the often manual and error-prone process of maintaining changelogs and version numbers in a development workflow.
Core Commands:
rune change: Interactive command to document changes before merging. Generates timestamped JSON files containing change details. Captures change type (major/minor/patch/none), description, author, and optional issue links
rune verify: CI-focused validation command. Ensures proper change files exist and are valid. Verifies branch differences and file naming conventions
rune apply: Processes accumulated change files. Automatically bumps version numbers based on change types. Updates CHANGELOG.md and package.json. Commits and pushes changelogs
Key Features: Automated Version Management - intelligently handles semantic versioning based on change types. Standardized Change Documentation - enforces consistent changelog formats. CI/CD Integration - built-in commands for verification in CI pipelines. Issue Tracking - optional integration with issue tracking systems. Git Integration - automated commit and push functionality.
Use Cases: Maintaining consistent changelog entries across team members. Automating version bumps based on change significance. Enforcing change documentation in CI/CD pipelines. Tracking changes with associated issue references. Standardizing release documentation
The tool essentially automates the often manual and error-prone process of maintaining changelogs and version numbers in a development workflow.
Core Commands:
rune change: Interactive command to document changes before merging. Generates timestamped JSON files containing change details. Captures change type (major/minor/patch/none), description, author, and optional issue links
rune verify: CI-focused validation command. Ensures proper change files exist and are valid. Verifies branch differences and file naming conventions
rune apply: Processes accumulated change files. Automatically bumps version numbers based on change types. Updates CHANGELOG.md and package.json. Commits and pushes changelogs