Update CHANGELOG.md directly when creating a release/tag

[ppuschmann]

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request.
• Please do not leave +1 or me too comments, they generate extra noise for issue followers and do not help prioritize the request.
• If you are interested in working on this issue or have submitted a pull request, please leave a comment.
• If an issue is assigned to a user, that user is claiming responsibility for the issue.
• Customers working with a Google Technical Account Manager or Customer Engineer can ask them to reach out internally to expedite investigation and resolution of this issue.

Description

In the current release management the contents of CHANGELOG.md is created (with some delay) after creating the tag / release.

This is then resulting in outdated information in the pull-requests/merge-requests that are generated by renovate.

The generated merge-requests will show (or link) to a CHANGELOG.md that still tells me:
"this new release is still unreleased", which is then a bit disappointing because

• I don't want to merge "unreleased" provider versions
• I don't see current changes (in most cases CHANGELOG.md not properly filled out)
• I have to do additional klicks to manually find out that the new provider-version is actually released and has a changelog

Some (small) discussion: renovatebot/renovate#32344

We'd like to see a even better orchestrated release management. :-)

Thank you so far for your work and support.

New or Affected Resource(s)

• release-management

Potential Terraform Configuration

References

renovatebot/renovate#32344

[wyardley]

I noticed the missing release notes on 6.10 too, good to know why that happened.

I had assumed it used release notes always, I think it used to, but that's also interesting.