@shenxianpeng I'm giving serious thought about revising the release process here.
The release-drafter project is not as well maintained as it once was (see release-drafter/release-drafter#1455). Given the complexity of the supported config, it is not surprising that maintenance has been lacking attention.

Auto label doesn't work

I think we need to use a separate config just for that auto-label feature (during a PR event).
And, for some reason, the release-drafter action tries to create/update a drafted release during a PR event, before it is merged (?!).

There must be a better way to auto label PR. Personally, I could do it with nushell and gh-cli...

Drafting releases

If releases are only focused on PRs, then commits pushed directly to main will not show up in the release notes 👎🏼.

I understand that release-drafter relies solely on PR/issue labels to categorize release notes. But release notes can be generated in a number of different ways.
I know git-cliff can use both PR labels and conventional-commit titles to categorize changes. Git-cliff can even "guess" the next version tag based on unreleased changes, but I don't often use that feature.