Review code changes, open coding issues, publish release notes. Every one is ready to run, and you can adjust it in plain language.
Date the approved release's changelog and post its link.
Your GitHub changelog stays current as pull requests merge, and your maintainer gets a dated section and link after release approval.
Publish categorized notes for each newly tagged release.
Your GitHub releases get readable notes as new tags arrive, with changes grouped by type and linked to commits.
Publish a changelog that matches the tagged release.
Your software changelog covers what shipped in the release, and your editor gets the public page link after publication.