Skip to content

Fix error when publishing packages from 'master' (v2)

Pablo Herrera requested to merge develop into master

Before creating the previous merge request, several tests were done in which packages were published using the usual branch model and publish procedure without encountering any problems. Unfortunately the merge request did not have the expected effect so this new merge request was created.

The problem is related to the use of Lerna's --conventional-graduate option, which allows publishing the stable version of a package that was in a non-stable version (for example, going from a version 1.0.0-alpha.0 to 1.0.0). Unfortunately this option causes errors during publishing and the causes could not be identified.

To avoid additional problems, the --conventional-graduate option was removed from the Lerna configuration. This implies that from now on new packages must start from version 1.0.0 in their package.json file and, when publishing it for the first time, Lerna will assign them version 1.1.0 (the first version corresponds to a new feature). Therefore, the initial version of a package will be 1.1.0.

There are alternative publishing methods which will be reviewed in the coming weeks.

Merge request reports