You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When auto creates a new release it also creates release notes from all changes which happened since the last release.
If a lot of changes have happened since the last release, those release notes can grow very big.
There is a character limit for a release to be created via the GitHub API of 125000 characters.
The result of too many changes is
Validation Failed: {"resource":"Release","code":"custom","field":"body","message":"body is too long (maximum is 125000 characters)"}
There is no option to make auto truncate the release notes if this happens. The workaround I used was to create a release manually and with that the changes since the last release to be used for the new auto release were small enough for it to work again.
To Reproduce
Create a lot of commits in a repo which are not released and then try to release with auto shipit.
Expected behavior
Some way to configure auto to not use the whole generated release notes for the GitHub release in case it gets to big. Another option would be that by default the release notes are truncated if they grow too big.
I think this is different #1294 since this is with the GitHub api. Would either of you be interested in submitting a PR? should be easy to cap the length of the posted comment
Describe the bug
When auto creates a new release it also creates release notes from all changes which happened since the last release.
If a lot of changes have happened since the last release, those release notes can grow very big.
There is a character limit for a release to be created via the GitHub API of 125000 characters.
The result of too many changes is
There is no option to make
auto
truncate the release notes if this happens. The workaround I used was to create a release manually and with that the changes since the last release to be used for the new auto release were small enough for it to work again.To Reproduce
Create a lot of commits in a repo which are not released and then try to release with
auto shipit
.Expected behavior
Some way to configure auto to not use the whole generated release notes for the GitHub release in case it gets to big. Another option would be that by default the release notes are truncated if they grow too big.
Screenshots
Environment information:
Additional context
The text was updated successfully, but these errors were encountered: