In summary: Henceforth releasenotes will consist of mostly automated dependency bumps and the same commit messages that you can also see in the commit history.
- The automated changelog is based on PR titles, which allows you to edit them without rewriting history, and labelling them for filtering/grouping.
[1] https://docs.github.com/en/repositories/releasing-projects-o...
@pronik's reply was spot on, viewing the merge commit, which shows which branches and tags the commit is included in. Example: https://github.com/openshift/okd/commit/e278fba2d8a5aea6b7bd...
I guess it's dependent on merge strategy, where squash merge will not include the initial commit hash. Or maybe "pr commit view" excludes the same info.