Skip to content
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

Proposal: don't store the version numbers #76

Open
jpnelson opened this issue Apr 6, 2017 · 0 comments
Open

Proposal: don't store the version numbers #76

jpnelson opened this issue Apr 6, 2017 · 0 comments

Comments

@jpnelson
Copy link

jpnelson commented Apr 6, 2017

I think a lot of the complexity around git pushing / pulling

#74
#32

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)

This would also partially solve the dry-run issue: #67

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant