Where does the proposed release note come from?
Release Please reads Conventional Commit messages, short descriptions that identify a change as a fix, feature or other type. It gathers release changes in a pull request, a proposed edit someone can review before merging. Review the version and change notes against the actual user-facing work.
Does a GitHub release put the package in a registry?
Merging the release pull request can produce a GitHub tag and release. A tag names the released point in the project’s history. Publishing to a package registry or deploying an app is a separate configured job. Review the merge permissions and any connected publishing step before activating it.
What should you keep if you replace Release Please?
Keep the commit history, release tags, configuration and changelog. The open-source tool does not sell the build workers it runs on. If you use GitHub Actions or another runner, check that service’s own allowance and permission rules.
Would a reader understand the change from its commit message?
On paper, write a fictional fix for a form button and a feature for adding a receipt download. Draft the release note a user should see.
- Check the proposed notesMake the fix and feature understandable without naming internal files.
- List the separate outputsMark the release pull request and the GitHub release. Leave registry publishing and app deployment out of the exercise.