Release Please

Release Please uses commit history as its input and turns release preparation into a review step. In an illustrative example, a project has commits such as feat: export deployment metadata and fix: handle empty changelog; the action can prepare a pull request with version and changelog changes. Review that diff before merging. The documented merge flow creates a tag and GitHub Release, so the output is a versioned release checkpoint rather than a compiled package. No repository or action was run for this listing.

The GitHub Action needs repository write permissions for contents, issues, and pull requests, and token behavior matters if later workflows should trigger from changes made by the action. It is release-specific tooling, not a general CI service, and does not publish artifacts to package managers by itself. The README says Release Please is not an official Google product.

Compared with the already listed Changesets, Release Please derives changes from commit history rather than asking contributors to add changeset files; Changesets has particular support for monorepo versioning. GoReleaser focuses on release engineering and artifact publishing, while Release Please is centered on preparing reviewed release pull requests.