lerna publish
Create a new release of the packages that have been updated. Prompts for a new version and updates all the packages on git and npm
Options
Name | Description |
---|---|
--concurrency | How many threads to use when Lerna parallelizes the tasks (defaults to count of logical CPU cores) |
--loglevel <loglevel> | What level of logs to report. On failure, all logs are written to lerna-debug.log in the current working directory |
--max-buffer <bytes> | Set a max buffer length for each underlying process call |
--no-progress | Disable progress bars. This is always the case in a CI environment |
--no-sort | The --no-sort option disables sorting, instead executing tasks in an arbitrary order with maximum concurrency |
--reject-cycles | Fail immediately if a cycle is found (in bootstrap, exec, publish or run) |
-h, --help | Show help |
-v, --version | Show version number |
--npm-tag <tagname> | Publish to npm with the given npm dist-tag (Defaults to latest) |
--canary, -c | Create a canary release |
--skip-git | Don't run any git commands |
--force-publish <packages> | Force publish for the specified packages (comma-separated) |