Join GitHub today
Lerna used in non conventional commit workflow not supported when manually selecting prerelease version and bump to release in CI #2219
In a Developer / Release workflow, where a developer manually selects the prelease version using lerna version, and the CI process automatically publishes the prerelease version to release version when merging to master.
See below steps for full workflow. It would be good if lerna version could work better with lerna publish and see the prerelease is from git and to enable publish to npm with the release version without having to go and manually do this in lerna version for a new commit.
Step 7. ci triggers build and publish to npm feed without the preid (when the version is non prerelease)
The issue here is, we're wanting developers to think about the version. We could go down the conventional commit path for this & considering this. But right now once prerelease is done, we want to run publish command in ci for the release version & not have to make any changes in the repo to force this through another version selection (no prerelease).
Another option I looked at without conventional commits is to use
But in CI situation I want the
Steps to Reproduce (for bugs)
<!-- Please paste your `lerna.json` here -->
As above this seems like a workflow limitation for a common developer release process.
| OS | Version |
@evocateur wondering if I can gain your expertise in this one? If valid use case around managing packages through git/tags with version prerelease and enabling bumping to release like publish canary then happy to perhaps work on this one to contribute to this great library.