We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
This may have been on purpose, but i do not see the behavior change listed under breaking changes. https://blog.npmjs.org/post/626173315965468672/npm-v7-series-beta-release-and-semver-major
VERSION=$(npm version patch) set tag to v1.0.1, but VERSION is 1.0.1
VERSION=$(npm version patch)
v1.0.1
1.0.1
NPM 6 behavior:
VERSION=$(npm version patch) set tag to v1.0.1, and VERSION is v1.0.1
npm init
echo $(npm version patch)
Node 10, Node 15, npm 7.5.2 Ubuntu and Mac Catalina.
The text was updated successfully, but these errors were encountered:
npm version <inc>
good catch! #2718 will fix this in the next release
Sorry, something went wrong.
this is fixed in npm@7.5.5 which was just published today
nlf
Successfully merging a pull request may close this issue.
This may have been on purpose, but i do not see the behavior change listed under breaking changes.
https://blog.npmjs.org/post/626173315965468672/npm-v7-series-beta-release-and-semver-major
Current Behavior:
VERSION=$(npm version patch)
set tag to
v1.0.1
, but VERSION is1.0.1
Expected Behavior:
NPM 6 behavior:
VERSION=$(npm version patch)
set tag to
v1.0.1
, and VERSION isv1.0.1
Steps To Reproduce:
npm init
echo $(npm version patch)
Environment:
Node 10, Node 15, npm 7.5.2
Ubuntu and Mac Catalina.
The text was updated successfully, but these errors were encountered: