Private packages should not be listed in publish success messages

Running lerna publish prompts for individual package versions for packages marked with private: true.

lerna publish
? Select a new version for @org/package-a
? Enter a custom version 1.0.0-alpha.1 # Forced to manually enter a dummy version

Changes:
 - @org/package-a: 1.0.0-alpha.1 => 1.0.0-alpha.1 (private) # This is confusing
 - @org/package-b: 1.0.0-alpha.1 => 1.0.0-alpha.1
 - ...

? Are you sure you want to publish the above changes? Yes
lerna info publish Publishing packages to npm...
lerna info published @package-b
lerna info git Pushing tags...
Successfully published:
 - @org/package-a: 1.0.0-alpha.1 => 1.0.0-alpha.1 # This is confusing
 - @org/package-b: 1.0.0-alpha.1 => 1.0.0-alpha.1
lerna success publish finished

While it doesn’t actually publish the private packages to NPM, the console output still shows it as published successfully.

[donaldpipowitch]

Well it “is” versioned in the sense of “it has a version”. But I don’t ever want or need to update the version, because they are never consumed by anyone.

[superkhau]

If we don’t prompt for them, what version are we supposed to use? Private packages are intended to still be versioned, just never published.

You’re right. Maybe we should add an option to skip versioning instead?

Package X@1.0.0-alpha is marked as private, skip versioning?

That way, the CLI tool can skip the other weird prompts below too.

As for sending a PR, my schedule is pretty full and won’t be available again till beginning of June. I’ll try to send then if someone doesn’t get around to it before me. 😉