That would be really very helpful! 👍
I already thought about this, the only thing is not always clear how to automatically classify PR (Added / Changed) 🤔

In fact, this can be done even at the stage of the release build, in order to avoid unnecessary bot commits(per each PR) and line conflicts, writing the entire block of changes at once.

the only thing is not always clear how to automatically classify PR (Added / Changed)

That would mean we need to introduce some commit guidelines, which wouldn't be so bad I think.
On the other hand: If the commit message is clear enough, maybe it would be enough to have only a list of commits in the changelog between the versions, but I'm not sure. Any other ideas?

I already thought about this, the only thing is not always clear how to automatically classify PR (Added / Changed) 🤔

There are two options to do that:

1. Follows Conventional Commits rules and uses prefixes: feat and fix in commits.
   To ensure that contributors follow these rules we can add the commitlint.
2. Uses labels like feature and changes.

I like more the first option. What do you think?

In fact, this can be done even at the stage of the release build, in order to avoid unnecessary bot commits(per each PR) and line conflicts, writing the entire block of changes at once.

I would think more how to implement this one, because I wouldn't like to have a lot of bot commits 😅

I personally like conventional commits :)

I also actively use conventional commits in other projects, so I would gladly vote for this idea 🙂