Beachball tries to merge no changes
viditganpi opened this issue · comments
Currently beachball does not have a mechanism to exit early and not perform any bump or publish in case there are no change files for non private packages. This later causes the publish command to fail at merge step, as there is nothing to merge.
A check should be added before bump and publish to tackle this case.
Probably a duplicate of #597. Beachball already exits early if there are no change files at all.
Yes, but it should also exit early in case there is change files only for private packages
Yes, that’s what the other issue is about. Until that’s fixed, you can delete the bad change files to avoid the problem. (I’ve usually only seen that happen around the time a package is initially changed from private to published.)