It seems like the prepare-release-branch.yml workflow already sets the release date as the current date in a pr, and we also maintain a list of our most current changes at the top, so we most likely do not need the update CHANGELOG step in main post release.yml workflow.
It seems like the prepare-release-branch.yml workflow already sets the release date as the current date in a pr, and we also maintain a list of our most current changes at the top, so we most likely do not need the update CHANGELOG step in main post release.yml workflow.