commitizen uses wrong version of cz-conventional-changelog

[rifler]

In my package.json:

...
"commitizen": "2.9.6",
"cz-conventional-changelog": "^2.1.0"
...

<projectDir>/.czrc:

{ "path": "cz-conventional-changelog" }
# I've also tried
# { "path": "./node_modules/cz-conventional-changelog" }

Then I run npm run cz (it is just simply git-cz) and get these questions:

? Select the type of change that you're committing: feat:     A new feature
? Denote the scope of this change ($location, $browser, $compile, etc.):
 
? Write a short, imperative tense description of the change:
 asd
? Provide a longer description of the change:
 qweqwe
? List any breaking changes or issues closed by this change:

Questions about breaking changes and issues are combined into one, but I googled, that in one of the new releases of cz-conventional-changelog this behaviour was changed - commitizen/cz-conventional-changelog#44

Ok, let's grep old combined message

grep -r "List any breaking changes or issues closed by this change" ./node_modules 

./node_modules/commitizen/node_modules/cz-conventional-changelog/engine.js:          message: 'List any breaking changes or issues closed by this change:\n'

And some code from related pull request

grep -r "breaking = breaking ? 'BREAKING CHANGE: ' + breaking.replace" ./node_modules

./node_modules/cz-conventional-changelog/engine.js:        breaking = breaking ? 'BREAKING CHANGE: ' + breaking.replace(/^BREAKING CHANGE: /, '') : '';

Then I noticed debug messages from commitizen:

npm run cz --loglevel=error

> @[email protected] cz /Users/rifler/Documents/projects/my-project
> git-cz

[email protected], [email protected] // <---this line


Line 1 will be cropped at 100 characters. All other lines will be wrapped after 100 characters.

? Select the type of change that you're committing: (Use arrow keys)

Why does it use 1.2.0, while I have 2.1.0 in ./node_modules/cz-conventional-changelog ?
It turns out that commitizen uses wrong version of cz-conventional-changelog - it own version, but not installed by myself.
Can you please help me with this strange behaviour ?
Thanks in advance

[rifler]

I've also tried ./node_modules/.bin/git-cz instead of npm run cz

./node_modules/.bin/git-cz 
[email protected], [email protected]

[travi]

although this is the documented suggestion for configuration, i don't understand how it would have ever worked to put the configuration in a .czrc file.

since the priority of config files gives package.json the highest priority, and the first existing file is used to pull out the config regardless of commitizen config actually existing in the file, it seems like this would always happen when config is not defined in package.json because it will fall back to config in your home directory when the config file it tried to read (always package.json since it will exist in all projects). my global config defines cz-conventional-changelog, which is don't have installed globally intentionally, but is a dependency of commitizen, which i do. notice that the version aligns with the incorrect version in @rifler's experience above:

└─┬ [email protected]
  └── [email protected] 

i noticed this inconsistency a long time ago when i first started using commitizen, but switched to the format used by the init command and didn't investigate deeply enough at the time. i recently ran into a problem when config is defined in the package.json, so i've reconsidered using the .csrc file again, only to find that it doesn't work.