{"bugs":{"url":"https://github.com/lerna/lerna/issues"},"dist":{"shasum":"dd4b95d1ed40211063bb546bba1581db4bab9b1a","tarball":"https://registry.npmjs.org/@lerna/version/-/version-3.8.5.tgz","fileCount":16,"integrity":"sha512-CfWoef3M2CCA3dMqPYJCrshuSAs+xCAEfVpLmaHQyutKXXGG1LZD38iq2Xs3dxNF07Md5H9+Mt6pfEwsXqjhJA==","signatures":[{"sig":"MEYCIQDD5Y2uiu8L7TBKhwdqDLPC9qm/n94hMS97BLb7dJ5wqQIhAPoM1xp6QBwf25C9BAdR6SPlUGn9bLQpKwI7omgbJdn2","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":52448,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJcMAYUCRA9TVsSAnZWagAAJLQP/iJj5huOQ4BkRtAM0sgL\n8CWA5+Z88JhM/MBibm0P5i5kMg8atR5Nyeu38rflru7kRWtw/2C7Bbfp/1Nq\nB0ysWTlOozfT4lhOdg9lorH73L4BpLpNZt23uMRu0vGPgaYCM6dmWdLiRN6v\nG9OalfloIgDiDTh8qq3qmUy7Gn9/kDe8frIr5bnbmgUVZ6NNp/UkkeWsIewu\nl7uJHbaDVZVMWq/Vi/AlZrGOtJw+5HxwThSP9cO42qczPipZSV6ZJzVd4Wsy\nsLe5N+0bVtY15QPaMZFwYcYBlD7HDQ43Pa4AzHZ3vIIbVp12ZFU41FhsMiEP\nBLZvMiB4LBEk1rBVHWTlNr9A4Eq/ZhIRUx5wHNv/S98lLbYTa812xHfcIIrl\nWRZfaeaPY//cen8pWJt2FQEvtGOdOJyUNJBUd5+CdtBiO/pCjPdnAnmL6AUJ\nb7x7t/0ZtSKgrKMl/X8GTuwqujmS7L7NW+j7ARnJZCGtZY08Qye04nQ2fSML\ndj9JfxQc5l786N6EZhuDzWVR8JOkqiW6d5a/qRC6+27n33hSYEjouZjVUCpV\nmzw6w59b089SJH9wxJ3XWVhFJFW9AQBSl2eRaYTiAAE05d4X69kN3MptLDvo\nlb+XA49oYgpwzOrdQrnIkIQV7W7HFGRr7r8D9u5udnYekSvVzyEUND8M6+4C\nmm+X\r\n=OUjd\r\n-----END PGP SIGNATURE-----\r\n"},"main":"index.js","name":"@lerna/version","author":{"url":"https://github.com/evocateur","name":"Daniel Stockman"},"readme":"# `@lerna/version`\n\n> Bump version of packages changed since the last release\n\n## Usage\n\n```sh\nlerna version 1.0.1 # explicit\nlerna version patch # semver keyword\nlerna version       # select from prompt(s)\n```\n\nWhen run, this command does the following:\n\n1. Identifies packages that have been updated since the previous tagged release.\n2. Prompts for a new version.\n3. Modifies package metadata to reflect new release.\n4. Commits those changes and tags the commit.\n5. Pushes to the git remote.\n\n## Positionals\n\n### semver `bump`\n\n```sh\nlerna version [major | minor | patch | premajor | preminor | prepatch | prerelease]\n# uses the next semantic version(s) value and this skips `Select a new version for...` prompt\n```\n\nWhen run with this flag, `lerna version` will skip the version selection prompt and [increment](https://github.com/npm/node-semver#functions) the version by that keyword.\nYou must still use the `--yes` flag to avoid all prompts.\n\n#### \"Graduating\" prereleases\n\nIf you have any packages with a prerelease version number (e.g. `2.0.0-beta.3`) and you run `lerna version` with and a non-prerelease bump (`major`, `minor`, or `patch`), it will publish those previously pre-released packages _as well as_ the packages that have changed since the last release.\n\n## Options\n\n- [`--allow-branch`](#--allow-branch-glob)\n- [`--amend`](#--amend)\n- [`--commit-hooks`](#--commit-hooks)\n- [`--conventional-commits`](#--conventional-commits)\n- [`--changelog-preset`](#--changelog-preset)\n- [`--exact`](#--exact)\n- [`--force-publish`](#--force-publish)\n- [`--ignore-changes`](#--ignore-changes)\n- [`--git-remote`](#--git-remote-name)\n- [`--git-tag-version`](#--git-tag-version)\n- [`--message`](#--message-msg)\n- [`--preid`](#--preid)\n- [`--push`](#--push)\n- [`--sign-git-commit`](#--sign-git-commit)\n- [`--sign-git-tag`](#--sign-git-tag)\n- [`--yes`](#--yes)\n- [`--include-merged-tags`](#--include-merged-tags)\n\n### `--allow-branch <glob>`\n\nA whitelist of globs that match git branches where `lerna version` is enabled.\nIt is easiest (and recommended) to configure in `lerna.json`, but it is possible to pass as a CLI option as well.\n\n```json\n{\n  \"command\": {\n    \"publish\": {\n      \"allowBranch\": \"master\"\n    }\n  }\n}\n```\n\nWith the configuration above, the `lerna version` will fail when run from any branch other than `master`.\nIt is considered a best-practice to limit `lerna version` to the primary branch alone.\n\n```json\n{\n  \"command\": {\n    \"publish\": {\n      \"allowBranch\": [\"master\", \"feature/*\"]\n    }\n  }\n}\n```\n\nWith the preceding configuration, `lerna version` will be allowed in any branch prefixed with `feature/`.\nPlease be aware that generating git tags in feature branches is fraught with potential errors as the branches are merged into the primary branch. If the tags are \"detached\" from their original context (perhaps through a squash merge or a conflicted merge commit), future `lerna version` executions will have difficulty determining the correct \"diff since last release.\"\n\nIt is always possible to override this \"durable\" config on the command-line.\nPlease use with caution.\n\n```sh\nlerna version --allow-branch hotfix/oops-fix-the-thing\n```\n\n### `--amend`\n\n```sh\nlerna version --amend\n# commit message is retained, and `git push` is skipped.\n```\n\nWhen run with this flag, `lerna version` will perform all changes on the current commit, instead of adding a new one.\nThis is useful during [Continuous integration (CI)](https://en.wikipedia.org/wiki/Continuous_integration) to reduce the number of commits in the project's history.\n\nIn order to prevent unintended overwrites, this command will skip `git push` (i.e., it implies `--no-push`).\n\n### `--commit-hooks`\n\nRun git commit hooks when committing the version changes.\n\nDefaults to `true`. Pass `--no-commit-hooks` to disable.\n\nThis option is analogous to the `npm version` [option](https://docs.npmjs.com/misc/config#commit-hooks) of the same name.\n\n### `--conventional-commits`\n\n```sh\nlerna version --conventional-commits\n```\n\nWhen run with this flag, `lerna version` will use the [Conventional Commits Specification](https://conventionalcommits.org/) to [determine the version bump](https://github.com/conventional-changelog/conventional-changelog/tree/master/packages/conventional-recommended-bump) and [generate CHANGELOG](https://github.com/conventional-changelog/conventional-changelog/tree/master/packages/conventional-changelog-cli)\n\n### `--changelog-preset`\n\n```sh\nlerna version --conventional-commits --changelog-preset angular-bitbucket\n```\n\nBy default, the changelog preset is set to [`angular`](https://github.com/conventional-changelog/conventional-changelog/tree/master/packages/conventional-changelog-angular#angular-convention).\nIn some cases you might want to change either use a another preset or a custom one.\n\nPresets are names of built-in or installable configuration for conventional changelog.\nPresets may be passed as the full name of the package, or the auto-expanded suffix\n(e.g., `angular` is expanded to `conventional-changelog-angular`).\n\n### `--exact`\n\n```sh\nlerna version --exact\n```\n\nWhen run with this flag, `lerna version` will specify updated dependencies in updated packages exactly (with no punctuation), instead of as semver compatible (with a `^`).\n\nFor more information, see the package.json [dependencies](https://docs.npmjs.com/files/package.json#dependencies) documentation.\n\n### `--force-publish`\n\n```sh\nlerna version --force-publish=package-2,package-4\n\n# force all packages to be versioned\nlerna version --force-publish\n```\n\nWhen run with this flag, `lerna version` will force publish the specified packages (comma-separated) or all packages using `*`.\n\n> This will skip the `lerna changed` check for changed packages and forces a package that didn't have a `git diff` change to be updated.\n\n### `--ignore-changes`\n\nIgnore changes in files matched by glob(s) when detecting changed packages.\n\n```sh\nlerna version --ignore-changes '**/*.md' '**/__tests__/**'\n```\n\nThis option is best specified as root `lerna.json` configuration, both to avoid premature shell evaluation of the globs and to share the config with `lerna diff` and `lerna changed`:\n\n```json\n{\n  \"ignoreChanges\": [\"**/__fixtures__/**\", \"**/__tests__/**\", \"**/*.md\"]\n}\n```\n\nPass `--no-ignore-changes` to disable any existing durable configuration.\n\n> In the following cases, a package will always be published, regardless of this option:\n>\n> 1. The latest release of the package is a `prerelease` version (i.e. `1.0.0-alpha`, `1.0.0–0.3.7`, etc.).\n> 2. One or more linked dependencies of the package have changed.\n\n### `--git-remote <name>`\n\n```sh\nlerna version --git-remote upstream\n```\n\nWhen run with this flag, `lerna version` will push the git changes to the specified remote instead of `origin`.\n\n### `--git-tag-version`\n\nCommit and tag versioned changes.\n\nDefaults to `true`. Pass `--no-git-tag-version` to disable.\n\nThis option is analogous to the `npm version` [option](https://docs.npmjs.com/misc/config#git-tag-version) of the same name.\n\n### `--message <msg>`\n\nThis option is aliased to `-m` for parity with `git commit`.\n\n```sh\nlerna version -m \"chore(release): publish %s\"\n# commit message = \"chore(release): publish v1.0.0\"\n\nlerna version -m \"chore(release): publish %v\"\n# commit message = \"chore(release): publish 1.0.0\"\n\n# When versioning packages independently, no placeholders are replaced\nlerna version -m \"chore(release): publish\"\n# commit message = \"chore(release): publish\n#\n# - package-1@3.0.1\n# - package-2@1.5.4\"\n```\n\nWhen run with this flag, `lerna version` will use the provided message when committing the version updates\nfor publication. Useful for integrating lerna into projects that expect commit messages to adhere\nto certain guidelines, such as projects which use [commitizen](https://github.com/commitizen/cz-cli) and/or [semantic-release](https://github.com/semantic-release/semantic-release).\n\nIf the message contains `%s`, it will be replaced with the new global version version number prefixed with a \"v\".\nIf the message contains `%v`, it will be replaced with the new global version version number without the leading \"v\".\nNote that this placeholder interpolation only applies when using the default \"fixed\" versioning mode, as there is no \"global\" version to interpolate when versioning independently.\n\nThis can be configured in lerna.json, as well:\n\n```json\n{\n  \"command\": {\n    \"publish\": {\n      \"message\": \"chore(release): publish %s\"\n    }\n  }\n}\n```\n\n### `--preid`\n\n```sh\nlerna version prerelease\n# uses the next semantic prerelease version, e.g.\n# 1.0.0 => 1.0.1-alpha.0\n\nlerna version prepatch --preid next\n# uses the next semantic prerelease version with a specific prerelease identifier, e.g.\n# 1.0.0 => 1.0.1-next.0\n```\n\nWhen run with this flag, `lerna version` will increment `premajor`, `preminor`, `prepatch`, or `prerelease` semver\nbumps using the specified [prerelease identifier](http://semver.org/#spec-item-9).\n\n### `--push`\n\nPush the committed and tagged changes to the configured [git remote](https://github.com/lerna/lerna/tree/master/commands/version#--git-remote-name)\n\nPass `--no-push` to disable.\n\n### `--sign-git-commit`\n\nThis option is analogous to the `npm version` [option](https://docs.npmjs.com/misc/config#sign-git-commit) of the same name.\n\n### `--sign-git-tag`\n\nThis option is analogous to the `npm version` [option](https://docs.npmjs.com/misc/config#sign-git-tag) of the same name.\n\n### `--yes`\n\n```sh\nlerna version --yes\n# skips `Are you sure you want to publish these packages?`\n```\n\nWhen run with this flag, `lerna version` will skip all confirmation prompts.\nUseful in [Continuous integration (CI)](https://en.wikipedia.org/wiki/Continuous_integration) to automatically answer the publish confirmation prompt.\n\n### `--include-merged-tags`\n\n```sh\nlerna version --include-merged-tags\n```\n\nWhen run with this flag, `lerna version` will also consider tags of merged branches\nwhile fetching changes for packages to update.\n\n## Deprecated Options\n\n### `--cd-version`\n\nPass the semver keyword to the [`bump`](#bump) positional instead.\n\n### `--repo-version`\n\nPass an explicit version number to the [`bump`](#bump) positional instead.\n\n### `--skip-git`\n\nUse [`--no-git-tag-version`](https://github.com/lerna/lerna/tree/master/commands/version#--git-tag-version) and [`--no-push`](https://github.com/lerna/lerna/tree/master/commands/version#--push) instead.\n\n> NOTE: This option **does not** restrict _all_ git commands from being executed. `git` is still required by `lerna version`.\n","engines":{"node":">= 6.9.0"},"gitHead":"9f5c824b2f15119c10003dcc709f3ca0da99a5fe","license":"MIT","scripts":{"test":"echo \"Run tests from root\" && exit 1"},"_npmUser":{"name":"evocateur","email":"daniel.stockman@gmail.com"},"homepage":"https://github.com/lerna/lerna","keywords":["lerna","command"],"deprecated":"Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.","repository":{"url":"git+https://github.com/lerna/lerna.git","type":"git"},"_npmVersion":"lerna/3.8.5/node@v10.15.0+x64 (darwin)","description":"Bump version of packages changed since the last release","directories":{},"maintainers":[{"name":"evocateur","email":"daniel.stockman@gmail.com"},{"name":"hzoo","email":"hi@henryzoo.com"}],"_nodeVersion":"10.15.0","dependencies":{"chalk":"^2.3.1","p-map":"^1.2.0","slash":"^1.0.0","dedent":"^0.7.0","libnpm":"^2.0.1","p-pipe":"^1.2.0","semver":"^5.5.0","p-reduce":"^1.0.0","minimatch":"^3.0.4","temp-write":"^3.4.0","p-waterfall":"^1.0.0","@lerna/output":"^3.6.0","@lerna/prompt":"^3.6.0","@lerna/command":"^3.8.5","@lerna/child-process":"^3.3.0","@lerna/run-lifecycle":"^3.8.2","@lerna/batch-packages":"^3.6.0","@lerna/collect-updates":"^3.8.1","@lerna/validation-error":"^3.6.0","@lerna/check-working-tree":"^3.8.1","@lerna/conventional-commits":"^3.6.0"},"publishConfig":{"access":"public"},"_hasShrinkwrap":false,"readmeFilename":"README.md","_npmOperationalInternal":{"tmp":"tmp/version_3.8.5_1546651155819_0.20490102194823456","host":"s3://npm-registry-packages"},"_id":"@lerna/version@3.8.5","version":"3.8.5"}