@lerna/log-packed - npm Package Versions

3.13.0 (2019-02-15)

Features

• conventional-commits: Bump conventional-changelog dependencies to pick up security fixes (d632d1b)
• listable: Output newline-delimited JSON with --ndjson (742781b)
• meta: Add repository.directory field to package.json (aec5023)
• meta: Normalize package.json homepage field (abeb4dc)

3.11.0 (2019-02-08)

Bug Fixes

• collect-updates: Improve logging, making ignored globs explicit (42e4a5c)
• collect-updates: Match dotfiles when ignoring changes (99eadc6)
• create: Bump camelcase (e58a1d0)
• deps: Explicit libnpmaccess ^3.0.1 (6ba3d1d)
• deps: Explicit libnpmpublish ^1.1.1 (a506d96)
• deps: Explicit npm-lifecycle ^2.1.0 (506ad6d)
• deps: Explicit npm-package-arg ^6.1.0 (4b20791)
• deps: Explicit npm-registry-fetch ^3.9.0 (a83c487)
• deps: Explicit npmlog ^4.1.2 (571c2e2)
• deps: Explicit pacote ^9.4.1 (44d05bf)
• deps: Explicit read-package-json ^2.0.13 (2695a90)
• deps: Remove unused libnpm (replaced by direct sub-packages) (1caeb28)
• filter-options: Require arguments to --scope and --ignore (4b81dad)
• publish: Correct silly log heading (f1dc3fc)

Features

• version: Create Github releases with --github-release (#1864) (f84a631), closes #1513

3.6.0 (2018-12-07)

Bug Fixes

• add: Validate local package version (#1804) (ed6e2db), closes #1799
• bootstrap: Omit local bundled dependencies (#1805) (8f5bdbb), closes #1775
• pkg: Exclude mocks from package tarball (4017f37)

Features

• add: Add --no-bootstrap option (89bb928)
• bootstrap: Support --force-local option (#1807) (25572af), closes #1763
• Migrate existing usage to libnpm (0d3a786), closes #1767
• create: Migrate npm info subprocess to libnpm.manifest (65a1d1b)
• listable: Add --toposort option (b387881), closes #1652
• npm-dist-tag: Use fetch API instead of CLI to make changes (54008c6)
• publish: Add a "from-package" positional argument (#1708) (16611be), closes #1648
• publish: Attempt profile retrieval before whoami endpoint during user validation (38097d8)

3.0.4 (2018-08-14)

Bug Fixes

• publish: Do not ping third-party registries (42f4fdd), closes #1560
• publish: Only pass --json to npm pack when npm >= 5.10.0 (71babce), closes #1558
• publish: Run publish from leaf nodes again (3d348ec), closes #1560

<a name="3.0.3"></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>