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

Please no "^" after "lerna publish" in my "package.json"s #2397

Closed
TokugawaTakeshi opened this issue Dec 29, 2019 · 2 comments
Closed

Please no "^" after "lerna publish" in my "package.json"s #2397

TokugawaTakeshi opened this issue Dec 29, 2019 · 2 comments

Comments

@TokugawaTakeshi
Copy link

All libraries versions in my package.json are exact (no ^):

image

After lerna publish, old versions of internal dependencies has been replaced to newest version, but begins from ^

image

There is no lerna publish -E option yet. Please provide something like it.

Expected Behavior

For the case of my monorepo (hikari-automation depends on hikari-es-extensions and hikari-frontend):

image

when I execute lerna publish -E and publish, for example, version 0.0.35, versions of hikari-es-extensions and hikari-frontend in package.json of hikari-automation must be 0.0.35, not ^0.0.35.

Current Behavior

Current version is 0.0.22, so lerna added ^ to it:
image

Possible Solution

Please add new option for lerna publish which makes possible "Expected Behavior" functionality.

Context

Maybe everything will be all right until all packages has same version, but I feel unsafety and irritation when see "^" in my package.json. It is not ASAP, but I ask you to fix it.

@evocateur
Copy link
Member

--exact is what you're looking for (lerna itself uses it via json config). It's an option of lerna version, but you can pass it to lerna publish as well*. There is no -E shorthand alias.

  • This implicit call of lerna version from lerna publish will be removed in the next major version.

@TokugawaTakeshi
Copy link
Author

Thank you for the answer!

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

No branches or pull requests

2 participants