@lerna/version - npm Package Versions

3.0.6 (2018-08-16)

Bug Fixes

• command: Silence goalpost logging when running a composed command (12b4280)
• create: Use whatwg-url instead of node 8.x-dependent URL class (8701b79)
• init: Consume lernaVersion from options, not instance property (89e31d2)
• npm-publish: Tip-toe around logging when emitting chunk to stdout (c027246)
• version: Pass --preid to selection prompt (23a30a0), closes #1214
• version: Prioritize --preid over existing prerelease ID (#1568) (f2c470a)

<a name="3.0.5"></a>

3.0.5 (2018-08-15)

Bug Fixes

• collect-updates: Remove period from committish log message (a97262c)
• filter-options: Allow --private to be configured from file (21e134c)
• global-options: Allow --sort to be configured from file (f4aed75)
• help: Insert line break before describing boolean negations (da2f886)
• options: Provide -y alias for --yes (3ea460c)
• publish: Add confirmation prompt before execution (47766e5), closes #1566
• publish: Get tagged packages from merge commit (#1567) (fc771d9)
• version: Log skipped publish when composed (89645b7)

<a name="3.0.4"></a>

3.0.2 (2018-08-11)

Bug Fixes

• conventional-commits: Pass --tag-version-prefix to changelog utilities (8ed7d83)
• conventional-commits: Provide fallback bump when releaseType is missing (e330f6f), closes #1551
• exec: Allow config files to override defaults (2335149)
• publish: Add default for --tag-version-prefix (f159442)
• publish: Allow disabling of registry and package verification (0bfdff5), closes #1552
• run: Allow config files to override defaults (f15b6fb)
• version: Allow config files to override defaults (bb1cfb5)
• version: Positional bump supersedes --conventional-commits when choosing version (a74c866)

<a name="3.0.1"></a>

3.0.0 (2018-08-10)

Bug Fixes

• add: Always use POSIX paths when computing relative file: specifiers (ffe354f)
• add: Support explicit & implicit relative file: specifiers (41f231f)
• create: Use filename without scope when generating imports from test file (acfd48b)
• publish: Improve npm pack experience (627cfc2)

Features

• changed: Support list output options (6ecdd83)
• list: Extract @lerna/listable utility (bf56018)
• list: Improve scriptability with several new options (2e204af)
• npm-publish: Add npmPack export (088ea54)
• package: Add tarball property (be453cd)
• publish: Run npm pack before npm publish (8d80b2c)
• publish: Validate npm registry and package access prerequisites (ebc8ba6), closes #55 #1045 #1347
• Add @lerna/log-packed module, extracted from npm (9c767ac)
• Split lerna version from of lerna publish (#1522) (8b97394), closes #277 #936 #956 #961 #1056 #1118 #1385 #1483 #1494

BREAKING CHANGES

• changed: The package names emitted to stdout are no longer prefixed by a "- ", and private packages are no longer displayed by default.

• list: The default output of lerna ls no longer shows version strings or private packages.

• The new alias lerna la resembles the old output, with the addition of relative path to the package

• The new alias lerna ll is a shortcut for the new --long option

• A new --parseable option has been added to aid magical piping incantations

• • --preid now defaults to "alpha" during prereleases:

  The previous default for this option was undefined, which led to an awkward "1.0.1-0" result when passed to semver.inc().

  The new default "alpha" yields a much more useful "1.0.1-alpha.0" result. Any previous prerelease ID will be preserved, just as it was before.

• --no-verify is no longer passed to git commit by default, but controlled by the new --commit-hooks option:

  The previous behavior was too overzealous, and the new option operates exactly like the corresponding npm version option of the same name.

  As long as your pre-commit hooks are properly scoped to ignore changes in package.json files, this change should not affect you. If that is not the case, you may pass --no-commit-hooks to restore the previous behavior.

<a name="3.0.0-rc.0"></a>