would be mitigated by a different approach – semantic release leaves 0.0.0-semantically-released in the package.json files.
I would propose committing code that has 0.0.0-semantically-released in the package.json files, and having a task lerna-semantic-release apply-versions that would apply the calculated version numbers, based on the current git history.
This apply-versions task would be run before bootstrapping, and the version numbers would be cleared (probably with a clear-versions task)
I think a lot of the complexity around git pushing / pulling
https://github.com/atlassian/lerna-semantic-release/issues/74 https://github.com/atlassian/lerna-semantic-release/issues/32
would be mitigated by a different approach – semantic release leaves
0.0.0-semantically-releasedin the package.json files.I would propose committing code that has
0.0.0-semantically-releasedin the package.json files, and having a tasklerna-semantic-release apply-versionsthat would apply the calculated version numbers, based on the current git history.This
apply-versionstask would be run before bootstrapping, and the version numbers would be cleared (probably with aclear-versionstask)This would also partially solve the dry-run issue: https://github.com/atlassian/lerna-semantic-release/issues/67