the thing is that the only people who are capable to do that are those who are involved with the development. and to write something about all the changes, someone would have to be involved or at least knowledgeable about a variety of aspects of the software.
The people who run this particular repo are pretty vigilant at tagging the issues. It's not necessarily comprehensive but you could try filtering by pr pending (also toggle the open/closed option at the top left; I can't find a way to display all of them together on codeberg)
"PR" = pull request. which is what it's called when someone makes a change to the code.
I am also not a developer but I like to nose around in these things. :) I'm sure you can understand the gist of a lot of them. Like we have "Strip whitespace of emails on login", "Add a "show password" option when logging in", "Email Address Confirmation Cannot be Re-triggered". Also things like "Actor is null in Page and Note" which means nothing to me.
You can also look directly at the pull requests. Not everything is discussed in the Issues first. It's not the case with every project but this one is reasonably clear for a non expert to look through. eg "Show full language names in smaller badges", "Add upvote color when an item is boosted" etc.