vercel/release

Generate changelogs with a single command

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 13 minutes ago
Type:CLI ToolCategory(s):CI/CD & ReleaseDevOps & Observability
Added to GitGenius on September 19th, 2026
Created on December 22nd, 2016
Open Issues & Pull Requests: 46 (+0)
GitHub issues: Enabled
Number of forks: 117
Total Stargazers: 3,585 (+0)
Total Subscribers: 74 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 0.0 hours
Mean response time: 0.0 hours
90th percentile: 0.0 hours
Tracked items: 1

Most active contributors

Sign in to see contributor activity.

Related repositories by overlapping contributors

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 3
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 766 days
Stale 30+ days: 3
Stale 90+ days: 2

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

No label distribution available yet.

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

Release is a command line tool that automatically generates GitHub Releases and populates them with commits made since the last release.

The tool solves the problem of manually creating release notes by automating changelog generation from commit history. It works by analyzing commits since the previous release, determining the semantic version bump (major, minor, or patch), and creating a GitHub Release with formatted change information. Developers can pre-define change types directly in commit messages using parenthetical annotations, and the tool supports pre-releases with custom suffixes like canary or beta versions.

The tool suits projects that want to streamline their release workflow without maintaining separate changelog files. It works well for teams already using GitHub and npm, particularly those following semantic versioning conventions. The project includes a custom hook system that allows filtering and reformatting release information before publication, letting teams add intro text, reorder changes, or exclude specific commits marked with the ignore keyword.

Development activity shows consistent maintenance with regular updates addressing user needs. The project accepts community contributions through its standard contribution process. The tool remains actively aligned with its original purpose of automating release creation for teams managing multiple repositories.