Auto-syncing local version to the registry is slightly weird #241

Affected Packages

@changesets/cli

Problem

I understand why this works this way but given the fact that changesets are called in the documentation and "intent to release" I find it strange and really surprising that having no changesets ever (when starting to use changesets) can cause an accidental publish when a local version has not been yet published to npm. Similarly this can happen when adding a new package without immediately wanting to release it.

Proposed solution

None at this moment.