postversion with yarn does not work as expected

[stovmascript]

postversion with yarn does not work as expected

[suside]

Not sure, I was testing inside project with

$ npm --version
6.0.1
$ yarn --version
1.6.0

and husky precommit enabled.
I will report back as soon as I figure out who and where exactly is setting those env's.

[suside]

Right, another || will definitely do the job.
But since workaround works I'm going to figure out what's going on underneath before doing any PRs.

[stovmascript]

Whoa, nice find! Is it possible that this variable name was also changed in some new version of npm, or is it really yarn only?

[stovmascript]

Well, nevertheless, I think we can just add another || for process.env.npm_config_version_git_tag right?

[leethree]

I'm seeing the same problem and @suside 's workaround works. Would be great if it can be fixed.

[suside]

So it seems they do have different names
https://github.com/yarnpkg/yarn/blob/master/src/registries/yarn-registry.js#L17
vs
https://github.com/npm/cli/blob/latest/lib/config/defaults.js#L150
I'm not sure why.

It seems that another || would be the best solution indeed.