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

Generates wrong publish command when using with private npm modules #239

Open
mischah opened this issue Mar 22, 2018 · 1 comment
Open

Comments

@mischah
Copy link

mischah commented Mar 22, 2018

Hej,

the following occured with [email protected] and having "private": true in my package.json

I used the following command:

$ standard-version --tag-prefix "--prerelease" "beta"

Actual output

✔ bumping version in package.json from 3.0.0-beta.0 to 3.0.0-beta.1
✔ bumping version in package-lock.json from 3.0.0-beta.0 to 3.0.0-beta.1
✔ outputting changes to CHANGELOG.md
✔ committing package-lock.json and package.json and CHANGELOG.md
✔ tagging release 3.0.0-beta.1
ℹ Run `git push --follow-tags origin master --tag prerelease` to publish

where --tag prerelease doesn’t make sense as a git flag:

$ git push --follow-tags origin master --tag prerelease
error: src refspec prerelease does not match any.
error: failed to push some refs to '[email protected]:micromata/baumeister.git'

Desired output

ℹ Run `git push --follow-tags origin master` to publish

Cheers, Michael

@Djiit
Copy link

Djiit commented Jul 6, 2020

Hey, was looking for somehting else but this is a duplicate of #294 and can be closed I think.

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

2 participants