Limit the number of leftovers listed

[chadwhitacre]

Nobody's going to read through a list of 1,000s of commits, may as well use git log at that point.

What's more, over-long changesets can lead to GitHub API failures.

[BYK]

I don't think you are still immune to body overflow as we can go over the length limit via Milestones. Quite hard but possible, so just noting.

[BYK]

Also sorry, didn't ever think we'd reach this kind of limit so quickly 😅

[chadwhitacre]

Yes, it's possible with Milestones but less likely, GitHub is capping the POST body at 125,000 bytes.

And no need to apologize, easy enough to fix. Thanks for reviewing! :)

[jan-auer]

I'm afraid this didn't work, at least the last release still contained >2000 lines from the changelog. I'll check if we forgot to bump the version in the publish repository (i.e. what's "latest". Edit: The fix was pushed to latest on Dockerhub).

On another note, I'm not sure how useful it is to list 24 commits out of a list of 1500-2000. Might as well leave it out completely.

Edit: Eureka! While publish uses the latest published craft, the release action uses the latest released craft.

[chadwhitacre]

While publish uses the latest published craft, the release action uses the latest released craft.

getsentry/publish#666