Changelog generation workflow

[SachinSahu431]

Describe your PR

This PR implements a changelog generation workflow. The proposed workflow aims to automate changelog entries, enhance accuracy, and reduce manual efforts.

The idea here is to have a Changelog section in the PR template. The author will use this section to write about the changes introduced in their PR. The type of change will be obtained from the labels associated with the PR.

When a release branch is created, a GitHub action will be triggered, which will aggregate changelog entries from all the commits made after the previous release, and raise an automated PR. This aggregated changelog entry will be added under the ‘Unreleased’ section of the CHANGELOG.md. This will allow the maintainer to edit it anytime quickly.

Please refer to Changelog Automation proposal for more information.

What type of PR is this?

/kind release-note-none

Changelog Entry

NONE

Related

This requires the other PRs to be merged:
#1517 #1518

Closes #1434

[kakkoyun]

LGTM. We need to see it in action. Do you have any screenshots?

[ArthurSens]

Things we discussed in our call today

• Let's include the release-branch in the PR title, so it's easier to understand what this changelog PR is about
• Let's add commit range diff between the previous review and what it is being included in the new release

[SachinSahu431]

Thanks for the review!

Here is one dummy PR that is created by this workflow: SachinSahu431#55

Screenshots:

[SachinSahu431]

According to the feedback received, I've made adjustments to the workflow so that it only triggers on release branches when the VERSION file is modified. Additionally, the Changelog file will now have an updated header with the latest version and date.

[bwplotka]

Sounds this work was paused. That's ok, we learned so much! We also removed other half finished CI jobs to avoid confusion. Thanks for all the work! We can get back to this one day 💪🏽