Should `lerna publish --canary` detect unpublished packages?
See original GitHub issueHi, more of a question than an issue.
I tried to canary publish a module that have not been published yet and lerna publish --canary
did not detect it.
lerna changed
did detect the module.
lerna publish from-package --canary
did detect the module but didn’t wanted to publish a canary version (which is understandable looking at the source code).
I was able to force the behavior I wanted with lerna publish --canary --force-publish="@scope/my-package"
but it’s not easily scalable.
It seems that this behavior is intended, so I’m wondering what are the reasons? Would publishing a canary version of a not-yet-published module be discussed?
Lerna version: 3.22.1 Mode: independent
Issue Analytics
- State:
- Created 3 years ago
- Reactions:4
- Comments:6
Top Results From Across the Web
Using Lerna with unpublished packages - Stack Overflow
While it does not affect lerna bootstrap , it's worth mentioning that packages that you do not want to be published should always...
Read more >@lerna/validation-error | Yarn - Package Manager
If for some reason you wish to opt in to the legacy task-runner implementation details (powered by p-map and p-queue ), you can...
Read more >@lerna/publish - npm Package Health Analysis | Snyk
The npm package @lerna/publish was scanned for known vulnerabilities and missing license, and no issues were found. Thus the package was deemed as...
Read more >rushstack/rushstack - Gitter
npm audit requires a package-lock.json file though, which the project directory ... do you guys know where I can find information on how...
Read more >Using Lerna with unpublished packages – iTecNote
Symlink together all Lerna packages that are dependencies of each other. ... Do I first have to publish the depended-upon packages to npm...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Thanks @LeonardDrs. If you are concerned about scalability of your workaround, you could go with
@evocateur was canary publishing meant to ignore changes in packages that have not been published yet? If not, I would be keen to contribute a fix.
Hi Folks 👋
You may or may not know that lerna is now under the stewardship of Nrwl (announcement here https://github.com/lerna/lerna/issues/3121), a company with a long history of not just producing valuable open-source software (OSS), but also backing others (at the time of writing, Nrwl has donated over $50,000 to OSS it hasn’t created, see https://opencollective.com/nx for full details).
Quite simply, Nrwl ❤️ OSS, and is committed to making lerna the best it can be. We use it ourselves.
In order to take this awesome project forward from its current state, it is important that we focus our finite resources on what is most important to lerna users in 2022.
With that in mind, we have identified this issue as being potentially stale due to its age and/or lack of recent activity.
Next steps:
We want to give you some time to read through this comment and take action per one of the steps outlined below, so for the next 14 days we will not make any further updates to this issue.
@LeonardDrs as the original author of this issue, we are looking to you to update us on the latest state of this as it relates to the latest version of lerna.
Please choose one of the steps below, depending on what type of issue this is:
A) If this issue relates to a potential BUG in the latest version of lerna:
B) If this issue is a FEATURE request to be added to the latest version of lerna:
C) If this issue is a QUESTION which is applicable to latest version of lerna:
D) If this issue is no longer applicable to the latest version of lerna:
If we do not hear from @LeonardDrs on this thread within the next 14 days, we will automatically close this issue.
If you are another user impacted by this issue but it ends up being closed as part of this process, we still want to hear from you! Please simply head over to our new issue templates and fill out all the requested details on the template which applies to your situation:
https://github.com/lerna/lerna/issues/new/choose
Thank you all for being a part of this awesome community, we could not be more excited to help move things forward from here 🙏 🚀