semantic-release / semantic-release/github
Failed step Publish because Body is too Long
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 534
- Forks
- 150
- Avg merge
- 1m
- Merged PRs (30d)
- 3
Description
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 ?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the @semantic-release/github release path that calls the GitHub createRelease API, then review how the first release's changelog becomes the request body. Use the issue thread and the reported error to determine whether a configuration option or handling change is expected; done means the publish step no longer fails on an oversized body.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, javascript
- Domain
- api, release
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 32/100