-
Notifications
You must be signed in to change notification settings - Fork 49
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
Plugin ends up abruptly without completition or error, making other plugins not to start #459
Comments
Not sure if it's the same issue, but I was seeing this due to not having the changelog preset package installed as well.
Edit: actually just rolled back to 19.0.5 of semantic-release and now it works 🤷 |
We are seeing this as well. Downgrading to The fact that it exits w/o error makes this particularly tricky to spot. |
Hi, I think I've found the root cause. So it will create let's say 1.0.0 tag without release notes on it (actually it's good for us since we don't need the whole project history on the rn). Then I remove this flag and on every other SV run, since it's now analyzing correctly syntexed commits. it generated the release notes and tags as it should. |
We seems to have run into semantic-release/release-notes-generator#459 trying to do the 3.0.0 release that contains 200+ commits
We seems to have run into semantic-release/release-notes-generator#459 trying to do the 3.0.0 release that contains 200+ commits
I think this might be related to this issue from the const stream = intoStream.object(parsedCommits).pipe(writer(changelogContext, writerOpts));
const changeLogContent = await stream.toArray();
return changeLogContent.join(''); seemed to solve the issue. This is a suggested method from the |
@andrew-welker Can you propose a PR 🙏 ? |
This is an attempt to workaround semantic-release/release-notes-generator#459.
as explained in #479 (comment), this appears to have been related to a bug in node that has since been fixed. are folks still seeing this on updated node versions? |
Yes, I experienced the same issue two nights ago when running Here's the run showing the issue (before I pinned it): |
I'm also seeing this as well using:
Dropping |
release-notes-generator from semantic-release 21.0.2 with node 18.16.0 still exhibits the same problem with default configuration for the plugin. It seems that the problem appears when there are more than a certain number of changes that need to be processed for a release, thus resulting in a large amount of notes. This is apparent especially when trying to cut an initial release (1.0.0) from a older repository with a lot of commits. |
Also running into this issue - it definitely appears to be in consolidating multiple commits and trying to generate a significant release notes. The problem is fairly difficult and we end up just commenting out release note generator , doing a release without any release notes which is less than ideal.
You can see it just stops after the generate notes step without any error in this case and succeeds but no release is generated. https://github.com/idexio/idex-sdk-js/actions/runs/8963899307/job/24614859968 In the action you can see it tried to generate notes from our first version (not sure why here but either way, it should not have broken this way and at least given some kind of error). I believe it to be an issue when trying to merge all the different notes together personally but I haven't tried to dig deeper so far.
|
Could your recent problem be related to the recent breaking changes in conventional-changelog packages? Please be sure you are pinning the major version of packages you are installing along with semantic-release to avoid upgrading before semantic-release ready for the breakages See #633 for more details |
Hi team,
I'm using semantic versioning on a few of our projects. I want to include it in existing projects that already have many releases. Since it's the initial run of sv on the project, it found a lot of commits to include in the initial release.
For some reason, the steps of this plugin finish abruptly, hence other sv plugins can't start (eg @semantic-release/changelog & @semantic-release/gitlab) for creation and publish of the tag.
I've set the debug mode, but can't get much info.
Here is the snippet of the CI job output (I've renamed sensitive info):
.releaserc config:
CI job definition:
Many thanks!
Dusan
The text was updated successfully, but these errors were encountered: