Should lerna publish --canary detect unpublished packages?

[LeonardDrs]

Coming from #2803:

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

Code hasn't changed since 3.22.1 so I'm guessing it happens as well on the latest Lerna version