Failed step Publish because Body is too Long

[ndtrung1307]

Hi, I'm config to use semantic-release to automate release for my Repo. But I met an issue when the first time I run release because the changelog store a lot of commit( Because it's first time release). Error message is below:

Any suggestion or config option for @semantic-release/github to minimise the body when call API github createRelease ?

[KMDEV99]

Having same issue here. @ndtrung1307 Have You found any solution yet?

[seansilvestri]

I'm having the same issue here. Is there an option to truncate the excess?

[travi]

i'm sure this is something that could be protected against, but has not been a priority since this is only the third request we've seen in the life of the project that i'm aware of. that limit is quite large. could you help us understand what is in your release notes to make the request so large?

[seansilvestri]

The release notes contain the list of all prior PRs and commits in the repo, which is large. For more context, this is a mono repo for terraform modules, so the issue now arises with introducing a new module. Used this as inspiration: https://github.com/tjtharrison/demo-multiple-terraform-modules We primarily need the versioning aspect, not the release notes since they aren't meaningful in our context. Can we leave them out as a whole?

[travi]

i have to start with a note to provide context for my comments. semantic-release does not officially support monorepos, but we try not to prevent using a monorepo structure with community supported additions like semantic-release-monorepo. that said, we don't provide support here for monorepo specific details. are you using one of the community supported monorepo addons? if so you may be able to get more support for the monorepo details in that repo.

The release notes contain the list of all prior PRs and commits in the repo, which is large

are you making sure that appropriate tags exist in the history of the repo for the previous existing version when you add a new module? the format of the tag might differ based on the monorepo addon that you are using for your monorepo structure, especially if you are versioning the modules independently (which we recommend in order for the versions for each module can be semantic). if the previous existing tag is in place, semantic-release will only include release notes about the commits since that previous version

i could see putting in a safeguard to avoid going beyond the limit, but i dont think you want all of those previous details included in your new releases anyway, right? if this is something that you can avoid, that could be for the best since i dont know when we will be able to prioritize such a safeguard

[travi]

please also see my comments on https://github.com/semantic-release/git/pull/263#issuecomment-2266086218. while the detail about committing during a release is not related to this situation, i expect several of the other details are. i'm interested to understand if any of the suggestions there help folks avoid this situation until we can determine an appropriate action here