Skip to content

Latest commit

 

History

History
596 lines (442 loc) · 33.5 KB

CHANGELOG.md

File metadata and controls

596 lines (442 loc) · 33.5 KB
Raw

v2.0.0-rc.4 (2017-04-27)

Now with less bugs! The --hoist flag works again, among other rc.3 bugfixes, and our logging is much more detailed now.

💥 Breaking Change

🚀 Enhancement

🐛 Bug Fix

💅 Polish

📝 Documentation

🏠 Internal

Committers: 3

v2.0.0-rc.3 (2017-04-18)

Barring show-stopping bugs, our goal is to cut v2.0.0 later this week. Big props to all of our brave users riding the bleeding edge of release candidates and reporting issues!

🐛 Bug Fix

lerna bootstrap --npmClient=yarn should no longer require --concurrency=1 to avoid yarn cache race conditions.

If you've ever encountered the error Error: spawn rimraf ENOENT, this should fix that. Turns out yarn doesn't match a behavior of npm when installing, and does not symlink transitive dependency binaries.

🏠 Internal

Committers: 2

v2.0.0-rc.2 (2017-04-13)

Inching ever closer to 🏁 v2.0.0!

Highlights: lerna exec learned some new tricks (thanks to execa), and multi-line commit messages on Windows should now work.

$ lerna exec echo \$LERNA_PACKAGE_NAME
# note the escaped $, so it evaluates in the subshell, not the current shell

Ever get tired of repeating yourself in all of the package deps with devDependencies on babel-cli or rimraf? Now, all you need to do is have them installed in the root, and the following replaces all that duplicate code:

$ lerna exec rimraf lib
$ lerna exec babel -- src -d lib

The -- is still useful for hiding args from lerna, but it isn't always necessary now. In the example above, I had to hide the -d from lerna's arg parser, but positional arguments are just fine. When in doubt, always append the command you want to run (e.g., babel src -d lib) after the --, after all other arguments to lerna exec.

🚀 Enhancement

lerna --help is a bit cleaner now

Usage: lerna <command> [options]

Commands:
  bootstrap                Link local packages together and install remaining package dependencies
  clean                    Remove the node_modules directory from all packages.
  diff <pkg>               Diff all packages or a single package since the last release.
  exec <command> [args..]  Run an arbitrary command in each package.
  import <pathToRepo>      Import the package in <pathToRepo> into packages/<directory-name> with commit history.
  init                     Create a new Lerna repo or upgrade an existing repo to the current version of Lerna.
  ls                       List all public packages
  publish                  Publish packages in the current project.
  run <script> [args..]    Run an npm script in each package that contains that script.
  updated                  Check which packages have changed since the last publish.

Global Options:
  --loglevel                       What level of logs to report.  [string] [default: "info"]
  --concurrency                    How many threads to use if lerna parallelises the tasks.  [number] [default: 4]
  --scope                          Restricts the scope to package names matching the given glob.
                                   (Only for 'run', 'exec', 'clean', 'ls', and 'bootstrap' commands)  [string]
  --ignore                         Ignore packages with names matching the given glob.
                                   (Only for 'run', 'exec', 'clean', 'ls', and 'bootstrap' commands)  [string]
  --include-filtered-dependencies  Include all transitive dependencies when running a command, regardless of --scope or --ignore.
  --registry                       Use the specified registry for all npm client operations.  [string]
  --sort                           Sort packages topologically (all dependencies before dependents)  [boolean] [default: true]
  -h, --help                       Show help  [boolean]
  -v, --version                    Show version number  [boolean]

When a command fails, all logs are written to lerna-debug.log in the current working directory.

For more information, find our manual at https://github.com/lerna/lerna

Targeted command help: lerna bootstrap --help

lerna bootstrap

Global Options:
  --loglevel                       What level of logs to report.  [string] [default: "info"]
  --concurrency                    How many threads to use if lerna parallelises the tasks.  [number] [default: 4]
  --scope                          Restricts the scope to package names matching the given glob.
                                   (Only for 'run', 'exec', 'clean', 'ls', and 'bootstrap' commands)  [string]
  --ignore                         Ignore packages with names matching the given glob.
                                   (Only for 'run', 'exec', 'clean', 'ls', and 'bootstrap' commands)  [string]
  --include-filtered-dependencies  Include all transitive dependencies when running a command, regardless of --scope or --ignore.
  --registry                       Use the specified registry for all npm client operations.  [string]
  --sort                           Sort packages topologically (all dependencies before dependents)  [boolean] [default: true]
  -h, --help                       Show help  [boolean]
  -v, --version                    Show version number  [boolean]

Options:
  --hoist       Install external dependencies matching [glob] to the repo root  [string] [default: '**']
  --nohoist     Don't hoist external dependencies matching [glob] to the repo root  [string]
  --npm-client  Executable used to install dependencies (npm, yarn, pnpm, ...)  [string]

We've got plenty of room to grow our documentation, PRs welcome!

🐛 Bug Fix

📝 Documentation

  • #748 Reference conventionalcommits.org website in README. (@bcoe)
  • #751 Update README.md and docs to better explain hoisting. (@kylecordes)

If you've ever had a question about hoisting, read @kylecordes's brilliant docs here!

🏠 Internal

Committers: 5

v2.0.0-rc.1 (2017-04-07)

A silent (but deadly) bug slipped into the last release. Many thanks to (@timdp) for discovering it.

🐛 Bug Fix

v2.0.0-rc.0 (2017-04-06)

🎉 It's the first release candidate of v2.0.0! 🎉

Highlights: Jest, CI automation improvements, and tons of internal refactoring!

We've been in "beta" for quite some time, and it's time for our versioning to better communicate changes and guarantee API stability.

Our goal is to focus on a few important bugfixes before pushing the big red button and cutting a v2.0.0 for realsies. Check out the milestone to see if you can help!

💥 Breaking Change

Our apologies if you were using this, but did you know it's been broken since before the first 2.x beta? We have better opportunities in the offing for helping folks reuse parts of our inner logic (a --json flag for lerna ls, perhaps?), and encourage those who have complex needs to join or start discussions in the issues.

🚀 Enhancement

  • #666 Create annotated git tags instead of lightweight tags. (@AlexLandau)
  • #665 Automate CHANGELOG updates and version bumps during publish with --conventional-commits flag. (@bcoe)
  • #607 Increment version by semver keyword with --cd-version flag. (@cif)
  • #641 Add prompts for prerelease versions. (@rtsao)
  • #647 Allow concurrency to be configured via lerna.json. (@gigabo)
  • #635 Switch to Jest. (@evocateur)
  • #714 Refactor unit tests into Jest idioms, adding integration tests. (@evocateur)

🐛 Bug Fix

💅 Polish

  • #655 Actually warn when a matching dependency version is not satisfied. (@evocateur)
  • #674 Appveyor status should reflect master, not latest. (@evocateur)

📝 Documentation

  • #736 Update FAQ.md with publish retry details. (@cdaringe)
  • #693 Add GitHub issue and pull request templates. (@evocateur)
  • #634 Add documentation about "watch" commands next to --no-sort. (@trotzig)

🏠 Internal

Committers: 17

v2.0.0-beta.38 (2017-02-28)

📦 🐈 Initial Yarn support and more!

🚀 Enhancement

  • #605 Add support for pluggable npm clients. (@gigabo)

We'll make yarn the default once we feel that it's more stable.

$ lerna bootstrap --npm-client=yarn
{
  "npmClient": "yarn"
}

Very important fix for Babel that we used in the last release. This prevents a timing issue when publishing where a module will try to download a package that isn't published yet because it is published before it's own dependency is published itself. We used to get many issues from users on non-public npm about "babel-types" not being found.

  • #475 Lerna checks for changes since most recent tag in the current branch (@)

We now check for changes since the most recent tag in the current branch, instead of the most recent tag in entire repository. This allows publishing older versions of a project in maintenance branches, as well as nightly releases from a feature branch.

Additionally, we now ensure that the user is in a non-detached branch because lerna can't publish without a valid git branch.

  • #608 Add a --stream option to the run command. (@gigabo)

Useful to get output for child processes immediately if using lerna run with a watch command

$ lerna run watch --stream

This will not create a temporary dist-tag called lerna-temp when publishing. Useful if your third party proxy doesn't support dist-tags.

$ lerna publish --skip-temp-tag

Defaults to running npm run test and npm run env

  • #598 Durable includeFilteredDependencies config via lerna.json. (@gigabo)
{
  "commands": {
    "bootstrap": {
      "includeFilteredDependencies": true
    }
  }
}
{
  "commands": {
    "run": {
      "sort": false
    }
  }
}
$ lerna publish --registry https://my-private-registry

🐛 Bug Fix

  • #601 Fix --ignore flag when globs are expanded to an array. (@rtsao)
  • #597 Support command config in either "commands" or "command". (@gigabo)
  • #586 Avoid exception after successful lerna diff. (@evocateur)

🏠 Internal

Committers: 11

v2.0.0-beta.37 (2017-02-08)

--include-filtered-dependencies now works with ls,exec,run as well!

  • Fixes an issue with --hoist (from previous release)

🚀 Enhancement

  • #581 Improve support for --include-filtered-dependencies. (@roblg)
  • #576 Install with no arguments. (@gigabo)
  • #569 Short-circuit out of install with no packages. (@gigabo)

🐛 Bug Fix

  • #574 Use correct logger method in Package method.. (@evocateur)
  • #568 Check if directories exist before removing during hoist. (@gigabo)

🏠 Internal

Committers: 5

v2.0.0-beta.36 (2017-02-02)

🐛 Bug Fix

v2.0.0-beta.35 (2017-02-01)

3 new flags:

--no-sort (only for run, exec and bootstrap)

By default, all tasks execute on packages in topologically sorted order as to respect the dependency relationships of the packages in question. Cycles are broken on a best-effort basis in a way not guaranteed to be consistent across Lerna invocations.

Topological sorting can cause concurrency bottlenecks if there are a small number of packages with many dependents or if some packages take a disproportionately long time to execute. The --no-sort option disables sorting, instead executing tasks in an arbitrary order with maximum concurrency.

--hoist (only for bootstrap)

Install external dependencies matching glob at the repo root so they're available to all packages. Any binaries from these dependencies will be linked into dependent package node_modules/.bin/ directories so they're available for npm scripts. If the option is present but no glob is given the default is ** (hoist everything). This option only affects the bootstrap command.

$ lerna bootstrap --hoist

Note: If packages depend on different versions of an external dependency, the most commonly used version will be hoisted, and a warning will be emitted.

This option may also be set in lerna.json with "hoist": true or "hoist": <glob>.

--nohoist (only for bootstrap)

Do not install external dependencies matching glob at the repo root. This can be used to opt out of hoisting for certain dependencies.

$ lerna bootstrap --hoist --nohoist=babel-*

This option may also be set in lerna.json with "nohoist": <glob>.

🚀 Enhancement

  • #507 Automatic hoisting of common dependencies. (@gigabo)
  • #547 Spawn child process for rimraf (speeds up lerna clean). (@roblg)
  • #543 [clean] Support --include-filtered-dependencies flag. (@roblg)
  • #412 Make bootstrap, exec and run commands execute packages in dependency order by default. (@seansfkelley)
  • #373 [Feature] Log stdout when commands fail. Closes #343.. (@seansfkelley)

🐛 Bug Fix

  • #542 Fixes issue: prepublish not running in dependencies with --scope --include-filtered-dependencies. (@roblg)

When running lerna bootstrap --scope foo --include-filtered-dependencies run prepublish task with the same flags.

📝 Documentation

🏠 Internal

Committers: 9

v2.0.0-beta.34 (2017-01-26)

🐛 Bug Fix

Committers: 1

v2.0.0-beta.33 (2017-01-25)

  • Drop Node 0.10/0.12/5
  • Custom publish commit message
  • Publish to a different remote
  • Publish exact versions instead of ^

Breaking change

Enhancement

Override default message with --message or -m

lerna publish -m "chore: Publish"
  • #508 [Feature] Allow git remote to be changed for publish. (@tdanecker)

Use a different git remote other than origin

lerna publish --git-remote upstream
  • #390 [Feature] Adds --include-filtered-dependencies flag for bootstrap command. (@lukebatchelor)

my-component and all of its dependencies will be bootstrapped

lerna bootstrap --scope my-component --include-filtered-dependencies
  • #426 Add support for hidden '--exact' flag. (@L8D)

Use exact versions ("2.1.3") instead of with ^ ("^2.1.3")

lerna publish --exact

Bug fix

  • #458 use message passed as argument to the static method input() in PromptUtilities. (@btiwaree)
  • #483 467: lerna bootstrap succeeds with 0 packages. (@doug-wade)
  • #454 Use close event to wait for spawned processes to finish. (@xaka)

Documentation

Committers: 9

v2.0.0-beta.32 (2017-01-04)

Bug fix

  • #435 Use symlinks with relative paths instead of absolute on non-windows environments (Closes #423).. (@JaapRood)
  • #440 Change testing NODE_ENV to "lerna-test" (Closes #406). (@ryb73)
  • #444 Use correct logger method for warnings. (@evocateur)

Committers: 3

v2.0.0-beta.31 (2016-12-14)

Enhancement

  • #365 Add support for configurable package locations. (@gigabo)

Lerna now supports packages outside of the packages/ directory!

Configured via an array of globs in lerna.json:

{		
  "lerna": "2.0.0-beta.31",		
  "version": "1.1.3",		
  "packages": ["packages/*"]		
}

No more confusion about what will actually get published!

example

Adds a --loglevel [silent|error|warn|success|info|verbose|silly] option.

Any logs of a higher level than the setting are shown. The default is "info".

Bug fix

Committers: 15