Changelog not formatted correctly

[janetkuo]

The v1.7.0-alpha.4 changelog generated from #39164 PR description has weird format:

cc @danwinship

[caesarxuchao]

cc @david-mcmahon

[danwinship]

Hm... I wonder if it's because the second line starts with a backtick? It would be easy to reword/rewrap to change that.

The "1. ..." "2. ..." section is also indented too much... I had written it to look right as plain text since that's how it got displayed in the release note field in the PR, but I guess it's supposed to be markdown?

[david-mcmahon]

Yeah, there's a bunch of translations happening here (pandoc) to get HTML formatted email notifications and md for the changelog from the same human curated md source extracted out of the PR descriptions.

Release notes really should be much simpler than this. There's no need to add an "Action Required" headline as that happens automatically with the release-note-action-required label and there's a lot of formatting going on in this release note (multiple paragraphs, indenting, numbering). KISS is best for release notes.

At this point, the release notes can be hand-modified within changelog as needed to correct any formatting issues.

[dchen1107]

We need to fix this, but I don't think this is the release blocker.

[k8s-github-robot]

[MILESTONENOTIFIER] Milestone Removed

@caesarxuchao @janetkuo

Important:
This issue was missing labels required for the v1.8 milestone for more than 7 days:

priority: Must specify exactly one of [priority/critical-urgent, priority/important-longterm, priority/important-soon].

Removing it from the milestone.

Additional instructions available here The commands available for adding these labels are documented here

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

Prevent issues from auto-closing with an /lifecycle frozen comment.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or @fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten
/remove-lifecycle stale

[fejta-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close