conventional-changelog/standard-version

:trophy: Automate versioning and CHANGELOG generation, with semver.org and conventionalcommits.org

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 3 minutes ago
Added to GitGenius on September 8th, 2026
Created on April 4th, 2016
Open Issues & Pull Requests: 309 (+0)
GitHub issues: Enabled
Number of forks: 763
Total Stargazers: 7,980 (+0)
Total Subscribers: 53 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 2.6 hours
Mean response time: 157.0 days
90th percentile: 29.9 days
Tracked items: 12

Most active contributors

Sign in to see contributor activity.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Issue API getrepoissuespagesummary failed: 429 Rate limit exceeded. Please try again later.

Detailed Description

Standard Version is a command-line utility that automates versioning and CHANGELOG generation using semantic versioning and Conventional Commits.

The tool solves the problem of manual version management and changelog maintenance by automating these tasks based on commit message conventions. It reads the current version from package files or git tags, analyzes commits following the Conventional Commits specification to determine the appropriate semantic version bump, generates a changelog from commit history, creates a commit with updated version files and changelog, and tags the repository with the new version number.

Developers should be aware that Standard Version is deprecated. The README explicitly recommends release-please as an alternative for GitHub users, and commit-and-tag-version as a fork for those unable to use GitHub Actions or who need to maintain Standard Version compatibility. The tool works best for Node.js projects out of the box, though it supports custom configuration through packageFiles, bumpFiles, and updaters for projects in other languages or with non-standard version file locations. It requires that your project follows the Conventional Commits specification for commit messages to function effectively.

The project maintains active continuous integration workflows and code coverage tracking. Development activity shows ongoing maintenance of the codebase alongside the deprecation notice, indicating the maintainers continue to support existing users while directing new adopters toward successor tools.