ossf security best practice: The project MUST provide, in each release, release notes that are a human-readable summary of major changes in that release to help users determine if they should upgrade and what the upgrade impact will be. The release notes MUST NOT be the raw output of a version control log (e.g., the "git log" command results are not release notes). Projects whose results are not intended for reuse in multiple locations (such as the software for a single website or service) AND employ contin

Apart from 2 releases, this is how we have been doing release notes.

- [ ] document in the release process docs that this is required.

Start with the release process documentation referenced in the issue and review how release notes are currently described for the two exceptions and other releases. Document that each release requires human-readable notes summarizing major changes and upgrade impact, rather than raw version-control output. Done means the requirement is clearly recorded in the release process docs.

Written by the indexing model from the issue text.