-
Notifications
You must be signed in to change notification settings - Fork 35
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
JSON message format invalid #4
Comments
Regarding the error with missing project name: the plugin reads this field from the npm package name defined in the current context. Maybe your project does not define such a name? |
After looking into this I realized that if you run semantic release outside of npm (such as a global package instead of as |
I can't reproduce/understand your problem regarding development. Maybe this is also relate. When running in a debugging environment I launch semantic release like this.
Please elaborate if this is still a problem. |
yes you are right. I run it with I tried to build a example to reproduce the error but with the very same config and version it is working. |
It definitely has something to do with the release notes posted in the slack message. Perhaps you can reproduce it with a git repo with many commits (in my case ~50) in the release notes. |
I now can reproduce it. The following config for semantic release is used:
With the command I generate 50 commits When I then start semantic release I check the docs and it says that within a block the text property must have a length < 3000. I created a pull request and would be glad, if you accept it and merge it into master. |
When I want to use this plugin I get the following error during the execution of the plugin with debug flag:
Also the emssage of the failure in slack does not contain the name of the project:
On a different project with exactly the same config it is working.
Can it be a problem of the length of the slack message?
This is the first run of semantic release and the release-notes are longer then the release-notes on the other project.
The project contains a releaserc.yml.
and these versions are defined within the package.json:
The text was updated successfully, but these errors were encountered: