Google play accumulated release notes?

Question

I have this problem that I was wondering about for a really long time, but quite surprisingly I was not able to google out anything on the topic. I say "surprisingly" because this has to be a very common scenario.

The question is more about the idea how google play application release notes are supposed to work.

Say I publish updates of my app on Internal track, or Alpha track quite often, but most of the updates do not make it to production because, obviously, bugs are found, fixed, and then new update is published and only after it all works OK, does the app get to the production channel.

Now for each of the testing releases there are release notes of course that contain only a a few things, but then the accumulated changes for production contain a lot of changes. However, when I finally promote a release to production, only the changes of that specific version are pre-filled in the release notes field. So it contains the changes against the latest testing release, but not all the changes that happened in all testing versions since the last production update.

There's this "Copy from previous release" button, but quite surprisingly, it only lets you select one version and not multiple versions (I would use it to pick all the testing releases since latest production and expect the tool to merge all of the release notes in one list) so that doesn't really help. Now I understand that this is not a universal solution as changes may come and go, and you could also be just fixing bugs that were introduced in between the testing versions, so it would not make sense to list such bug fixes in production release notes. But you could still merge those and then go over and review the changes manually.

But again, I am not really asking for a technical solution on how to accumulate the changes, but more about the philosophy of how should I tackle this kind of problem in general. How is this problem usually solved?

Thanks!