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

docs(readme): Update semantic-release setup cmd #62

Closed
wants to merge 1 commit into from

Conversation

kentcdodds
Copy link
Contributor

The image needs to be updated as well because that's not what happens anymore.

@boennemann
Copy link
Member

The cli exposes itself as semantic-release-cli, to avoid confusion with the semantic-release core package, which is available as semantic-release. Unless I'm missing something the docs are correct the way they are :) But you're right, the CLI screenshot needs an update, w/o the info logs, and w/o passwords :)

@kentcdodds
Copy link
Contributor Author

When I npm install -g semantic-release-cli the command I then execute is semantic-release setup not semantic-release-cli setup. semantic-release-cli command is not found.

@boennemann
Copy link
Member

The semantic-release core used to have a setup command in older versions. I seems like you're running this old version globally installed. We've split that out, to keep the core as small as possible.

The CLI definitely exposes itself as semantic-release-cli https://github.com/semantic-release/cli/blob/master/package.json#L6
I'm confused as to why npm install -g semantic-release-cli doesn't give you that executable.

Can you run which semantic-release, or uninstall semantic-release globally and then only install npm i -g semantic-release-cli again. Also what's npm -v?

Thanks for your help!

@kentcdodds
Copy link
Contributor Author

Huh, that was odd. It's working now:

screen shot 2015-08-20 at 8 09 43 am

@kentcdodds kentcdodds closed this Aug 20, 2015
@kentcdodds kentcdodds deleted the patch-1 branch August 20, 2015 14:10
@boennemann
Copy link
Member

@kentcdodds Thanks for clarifying. To me this looks like the first time you didn't npm install -g semantic-release-cli, but npm install -g semantic-release. You then ended up with the "old" semantic-release as a global install, which also has a setup command. I say "old", but it's still the "latest" semantic-release, because I want to address some more things in the current "next" branch before moving them over.

Glad it's working now 👍

@boennemann
Copy link
Member

Just to document this here: 4.x is now on the "latest" dist-tag, which means this should no longer happen in the future :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants