googleapis/release-please

generate release PRs based on the conventionalcommits.org spec

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 42 minutes ago
Added to GitGenius on September 8th, 2026
Created on April 25th, 2019
Open Issues & Pull Requests: 352 (+0)
GitHub issues: Enabled
Number of forks: 587
Total Stargazers: 7,469 (+1)
Total Subscribers: 69 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 0.0 hours
Mean response time: 8.3 days
90th percentile: 15.0 hours
Tracked items: 316

How this project is maintained

Around half of the issues opened in the past year never receive a reply. 99% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. 63% of tracked open issues have had no activity in three months, so the open count overstates what is actively being worked. Only 2% of issues opened in the past year have been closed. Three people close 64% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 216
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 608 days
Stale 30+ days: 183
Stale 90+ days: 149

Recent activity

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

Top labels

  • priority: p3 (266)
  • type: bug (142)
  • type: feature request (109)
  • type: question (64)
  • priority: p2 (37)
  • help wanted (14)
  • needs design (7)
  • priority: p1 (4)

Detailed Description

Release Please is a GitHub Actions tool that automates CHANGELOG generation, version bumping, and GitHub release creation by parsing Conventional Commit messages from your git history.

The tool solves the problem of manual release management by maintaining Release PRs that stay synchronized with your codebase. It parses commits prefixed with `fix:`, `feat:`, and breaking change indicators to determine semantic version increments, then automatically updates changelog files, tags releases, and creates GitHub releases when the Release PR is merged. The approach keeps release decisions visible and reviewable as pull requests rather than automating them invisibly.

Release Please suits projects that adopt Conventional Commits and want to reduce release overhead without handling publication to package managers. It works best with squash-merge workflows to maintain a linear git history, which the tool recommends for cleaner bisecting and more meaningful changelogs. The tool does not manage complex branch strategies or automate publishing to npm, PyPI, or other registries—those steps remain manual or require separate tooling.

The project maintains active engagement with release cycles and incorporates feedback from real-world usage patterns. Development shows responsiveness to issues and pull requests from the community. The codebase receives regular updates to support new languages and frameworks beyond its initial Google Cloud client library origins.