Skip to content
This repository has been archived by the owner on Jul 17, 2023. It is now read-only.

Update lerna to the latest version 🚀 #56

Closed
wants to merge 1 commit into from

Conversation

greenkeeper[bot]
Copy link
Contributor

@greenkeeper greenkeeper bot commented Aug 10, 2018

Version 3.0.0 of lerna was just published.

Dependency lerna
Current Version 2.11.0
Type devDependency

The version 3.0.0 is not covered by your current version range.

If you don’t accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.

It might be worth looking into these changes and trying to get this project onto the latest version of lerna.

If you have a solid test suite and good coverage, a passing build is a strong indicator that you can take advantage of these changes directly by merging the proposed change into your project. If the build fails or you don’t have such unconditional trust in your tests, this branch is a great starting point for you to work on the update.


Release Notes v3.0.0

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

BREAKING CHANGES

lerna changed

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

lerna ls

  • 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

lerna publish

  • --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, justas 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.

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper bot 🌴

@coveralls
Copy link

Coverage Status

Coverage remained the same at 99.51% when pulling 3acc7c1 on greenkeeper/lerna-3.0.0 into 69f9fc9 on master.

greenkeeper bot added a commit that referenced this pull request Aug 10, 2018
@greenkeeper
Copy link
Contributor Author

greenkeeper bot commented Aug 10, 2018

Version 3.0.1 just got published.

Update to this version instead 🚀

Release Notes v3.0.1

Bug Fixes

  • publish: Allow unpublished packages to pass access verification (3a7348c)
Commits

The new version differs by 2 commits.

  • bf530b8 chore(release): publish v3.0.1
  • 3a7348c fix(publish): Allow unpublished packages to pass access verification

See the full diff

greenkeeper bot added a commit that referenced this pull request Aug 11, 2018
@greenkeeper
Copy link
Contributor Author

greenkeeper bot commented Aug 11, 2018

Version 3.0.2 just got published.

Update to this version instead 🚀

Release Notes v3.0.2

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)
Commits

The new version differs by 9 commits.

  • 784d64e chore(release): publish v3.0.2
  • e330f6f fix(conventional-commits): Provide fallback bump when releaseType is missing
  • a74c866 fix(version): Positional bump supersedes --conventional-commits when choosing version
  • 8ed7d83 fix(conventional-commits): Pass --tag-version-prefix to changelog utilities
  • 0bfdff5 fix(publish): Allow disabling of registry and package verification
  • f159442 fix(publish): Add default for --tag-version-prefix
  • bb1cfb5 fix(version): Allow config files to override defaults
  • f15b6fb fix(run): Allow config files to override defaults
  • 2335149 fix(exec): Allow config files to override defaults

See the full diff

greenkeeper bot added a commit that referenced this pull request Aug 11, 2018
@greenkeeper
Copy link
Contributor Author

greenkeeper bot commented Aug 11, 2018

Version 3.0.3 just got published.

Update to this version instead 🚀

Release Notes v3.0.3

Bug Fixes

  • publish: Restore deprecated --skip-npm functionality (cb47cb6), closes #1553
Commits

The new version differs by 2 commits.

  • 0dea7f4 chore(release): publish v3.0.3
  • cb47cb6 fix(publish): Restore deprecated --skip-npm functionality

See the full diff

@greenkeeper greenkeeper bot closed this Aug 13, 2018
@greenkeeper greenkeeper bot deleted the greenkeeper/lerna-3.0.0 branch August 13, 2018 14:02
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant