-

[ro0NL]

[HonkingGoose]

What about all these things?

Some things that come to mind about your idea:

• How to grab and combine the changelogs for say 500 dependencies that changed?
• What to do when we can't find a changelog for a dependency? List it as "no changelogs found", so that user knows Renovate tried?
• What to do when we hit the platform's PR body text limit?
  • Create message that explains to end-user that Renovate hit the platform limit
  • Stop processing new changelogs in time so we can add the message from above
• Fetching changelogs for 500 dependencies may cause Renovate to run into rate-limits, which makes the process slow.
• What happen when we scale this from one user to all Renovate users?
• Merge release notes #8177

Maintainers decide what to do

I'll let the Renovate maintainers weigh the above, and let them decide about this feature request.

Possible workaround

In the meantime, you may want to try the Octoclairvoyant website where you can compare between versions of dependencies.

[HonkingGoose]

I haven thought about scalability 😅

Well now you do! 😄

Generally to bypass PR body text limit, the bot could continue with comments instead.

I'll let the maintainers decide if this is a good idea or not.

Perhaps it can be put behind a checkbox.

Oh like a "if you want to see the changelogs, select this checkbox"-thing? That at least spreads the server-load, because users won't select the checkbox all at the same time. But that relies on users to be on their best behavior. I expect some users to automate selecting that checkbox... 🙃

Here's a wild thought, what if renovate hosts this app and links to it in PRs accordingly ...

I think we're open to get a PR (from somebody that's not us) for this. See my comment: #8177 (comment)

[rarkins]

I'm not in favor of posting changelogs for every dependency, because I know nobody will read them all, and then it's worse than pointless, because it's also noisy.

A compromise may be to post changelogs only for direct dependencies which have been updated, but at the same time you should be receiving individual PRs with changelogs for those anyway.

In general, I'm not in favor of this because I think it will be complex to implement, noisy in practice, and unlikely to be used - nobody's got time to read so much changelogs.

[HonkingGoose]

It's really hard to convert "whatever text a human can put into a changelog" into something that Octoclairvoyant understands, and can show neatly. So the "put Octoclairvoyant into Renovate"-thing would only be for explictly approved "sane SemVer changelog packages". That way nobody goes to Octoclairvoyant only to end up dissapointed. 😄