rea-changelog-update

Topics in the source

• REA changelog update
• Inventory before prose
• Write for users and retain credit
• Finalize with Release Please

Use this for release-note preparation and contributor attribution. Read docs/development/releasing.md from the repository root for publication authority and the existing checkpoint checks. This skill prepares notes; it does not authorize merging, tagging, or publishing. Fetch complete history and tags. Select the published baseline tag from .release-please-manifest.json on the release PR's base branch, and pin that branch's exact SHA as the editorial target. REA tags are rea-agents-VERSION. Use the proposed version, including its prerelease suffix; do not change the always-bump-minor strategy to imitate OpenClaw's calendar versions. Read the inventory, not just the existing bot draft. It includes side-branch commits, GitHub-associated PRs whose merge commits are in the range, commit authors/co-authors, and confirmed closing issues with their reporters. GitHub connections are paginated. Network errors stop generation; rerun into a new output file after recovery. Existing output files are never overwritten. Unresolved commit identities are retained as names/emails with user: null; never guess a handle or thank the merger as a substitute. The report preserves unknowns. This is a revie

This is an excerpt. Refer to the complete source and its current requirements.