You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello! I'm using standard-version in my private package, and the private package never is published. So my request is if the package.json has private:true, then the result doesn't display the npm publish.
$ standard-version patch
✔ bumping version in package.json from 1.0.4 to 1.0.5
✔ outputting changes to CHANGELOG.md
✔ committing package.json and CHANGELOG.md
✔ tagging release 1.0.5
++ ℹ Run `git push --follow-tags origin master` to publish-- ℹ Run `git push --follow-tags origin master; npm publish` to publish
Thanks.
The text was updated successfully, but these errors were encountered:
watilde
added a commit
to watilde/standard-version
that referenced
this issue
Sep 12, 2016
Hello! I'm using
standard-version
in my private package, and the private package never is published. So my request is if thepackage.json
hasprivate:true
, then the result doesn't display thenpm publish
.Thanks.
The text was updated successfully, but these errors were encountered: