Skip to content
New issue

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

Should not suggest npm publish if the package is private #102

Closed
watilde opened this issue Sep 12, 2016 · 0 comments
Closed

Should not suggest npm publish if the package is private #102

watilde opened this issue Sep 12, 2016 · 0 comments

Comments

@watilde
Copy link
Contributor

watilde commented 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 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.

watilde added a commit to watilde/standard-version that referenced this issue Sep 12, 2016
It should not suggest `npm publish` if the package.json
has `private: true`
watilde added a commit to watilde/standard-version that referenced this issue Sep 12, 2016
It should not suggest `npm publish` if the package.json
has `private: true`.
stevemao pushed a commit that referenced this issue Sep 12, 2016
It should not suggest `npm publish` if the package.json
has `private: true`.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

1 participant