What ReleaseMind reads
Drafts are compiled from release tags, merged pull requests, and commit history.
If you create a GitHub Release directly, ReleaseMind can still refresh and summarize it.
Draft quality improves when PR titles and descriptions are clear.
Inputs that improve drafts
Use consistent labels or prefixes on PRs to group changes cleanly.
Keep release tags aligned with the default branch to avoid missing commits.
Document breaking changes in PR descriptions so they surface in summaries.
When to regenerate
If you merge more PRs or update a tag, regenerate the draft to capture the latest changes.
Regenerate after fixing labels or PR titles so the grouping updates.
What counts as a release boundary
ReleaseMind uses tag boundaries to decide what belongs in a draft.
Avoid moving tags after publishing if you want clean history.
Pre-release tags are treated as separate boundaries from stable tags.
Review and introspect
Your inputs determine the quality of every draft.
- Are you giving ReleaseMind high-quality inputs (tags, PR titles, labels)?
- Is your team aligned on where a release starts and ends?
- Do you need to adjust tag cadence to match your shipping rhythm?