docs: trim changelog to user-facing items and clarify release notes guidelines

This commit is contained in:
Mohamed Boudra
2026-02-19 13:13:49 +07:00
parent 810ac63e21
commit 5db14ee50c
2 changed files with 5 additions and 5 deletions

View File

@@ -195,7 +195,10 @@ Notes:
- The website Mac download CTA URL is derived from `packages/website/package.json` version at build time, so no manual update is required after release.
Release completion checklist:
- Manually update CHANGELOG.md with release notes, between current release vs previous one, use Git commands to figure out what changed
- Manually update CHANGELOG.md with release notes, between current release vs previous one, use Git commands to figure out what changed. The notes are user-facing:
- Ask yourself, what do Paseo users want to know about?
- Include: New features, bug fixes
- Don't include: Refactors or code changes that are not noticeable by users
- `npm run release:patch` completes successfully.
- GitHub `Desktop Release` workflow for the new `v*` tag is green.
- GitHub `Android APK Release` workflow for the same tag is green.