-
Notifications
You must be signed in to change notification settings - Fork 3.7k
Closed
Labels
Bugthing that needs fixingthing that needs fixingRelease 7.xwork is associated with a specific npm 7 releasework is associated with a specific npm 7 release
Description
Current Behavior:
Executing npm version --no-git-tag-version
creates a Git tag and a Git commit with the incremented version in package[-lock].json
. Same behavior with --git-tag-version false
and --git-tag-version=false
.
Expected Behavior:
It only changes the version
in package[-lock].json
and does not create a Git commit/tag, as the docs suggest (https://github.com/npm/cli/blob/latest/docs/content/cli-commands/npm-version.md#git-tag-version), and like done by npm v6.
Steps To Reproduce:
- Enter the root directory of a package
- Execute
npm version --no-git-tag-version patch
- Find version tag and commit in Git history
Environment:
- OS: Windows 10, Ubuntu 18.04 (via WSLv1, Windows 10)
- Node: 12.19.0, 12.13.0
- npm: 7.0.1
pablote and oli-1
Metadata
Metadata
Assignees
Labels
Bugthing that needs fixingthing that needs fixingRelease 7.xwork is associated with a specific npm 7 releasework is associated with a specific npm 7 release