Skip to content

"major version zero" behavior in docs is inaccurate #4192

@iameli

Description

@iameli

Documentation issue

  • Reporting a typo
  • Reporting a documentation bug
  • Documentation improvement
  • Documentation feedback

Is there a specific documentation page you are reporting?

https://lerna.js.org/docs/features/version-and-publish#synchronized-versions

Additional context or description

There's a note on this page that says:

Note: If you have a major version zero, all updates are considered breaking. Because of that, running lerna publish with a major version zero and choosing any non-prerelease version number will cause new versions to be published for all packages, even if not all packages have changed since the last release.

I have a major version zero and I have chosen a non-prerelease version number (0.6.39).

 ▶ npx lerna publish
(node:77965) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.
(Use `node --trace-deprecation ...` to show where the warning was created)
lerna notice cli v8.2.2
lerna info current version 0.6.38
lerna info Looking for changed packages since v0.6.38
? Select a new version (currently 0.6.38) Patch (0.6.39)

Changes:
 - @streamplace/app: 0.6.38 => 0.6.39 (private)
 - streamplace-docs: 0.6.38 => 0.6.39

? Are you sure you want to publish these packages? (ynH)

Instead of publishing all packages, it's publishing only changed packages. This seems like reasonable behavior, but what are the docs talking about?

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions