Make release notifications useful again

[jrfnl]

@peter-evans Thank you for this action and the other actions you maintain!

I'd just like to make a small suggestion regarding the release notifications - while I totally understand that auto-generating those saves maintainer time, it also means the release notifications as they are now, are next to useless and wastes maintainer time on the other side.

It is my firm believe that changelogs are for humans and all CI/test/doc updates which do not impact end-users should just be grouped under a single "Various housekeeping, including improvements to the tests and documentation." entry in a changelog.

If, and only if, a dependabot update is relevant for end-users, it can be mentioned in the changelog, but only with a single entry per dependency.

Example from the 4.0.0 release (and I'm not even sure this one is relevant for end-users):
Instead of having 56(!!) "build(deps-dev): bump @types/node from x.x.x to x.x.x by https://github.com/dependabot[bot] in #..." entries in the release notification, one would have sufficed and would have made the release notification infinitely more readable:

• Dependency update: @types/node from 18.19.8 to 18.19.127 by https://github.com/dependabot[bot] in...

Even grouping the changelog entries into the typical semver "Added'/"Changed"/"Removed"/"Fixed"/"Maintenance" categories (where everything in "maintenance" can be ignored by non-contributors) would already help.

The problem with the release notifications as they are now, is that it takes every single person trying to find out what has changed at least five minutes to figure out what the relevant changes are, which is five minutes wasted per project depending on this action (and others).

Case in point: I'm currently trying to figure what has changed in the 4.0.0 release to make my CI builds fail with a "Error: Parameter token or opts.auth is required" error, but am struggling to find the relevant change entry.

I hope you'll at least consider my request, but respect your decision either way.

[adil192]

I'm currently trying to figure what has changed in the 4.0.0 release to make my CI builds fail with a "Error: Parameter token or opts.auth is required" error, but am struggling to find the relevant change entry.

In case yours is the same situation as mine, it was just that the dependabot PR didn't have access to secrets. After merging, the token or opts.auth error goes away.

[jrfnl]

@adil192 Yeah, I figured that out and actually added the secrets to the separate Dependabot secrets section in settings (to save me from having to investigate this again the next time).

Still, would have been a lot easier to spot without having to wade through a lot of useless changelog entries.