no access token supplied

[cedricdelpoux]

I tried multiple times to use the script semantic-release-cli setup but every time I get the error:

I also tried to pass npm and github token options semantic-release-cli setup --gh-token=<TOKEN> --npm- token=<TOKEN> but the error is the same:

I also tried to export those tokens on my .bashrc with no luck.

Token are created well on Github and Npm. I verified on the websites.

[IlyaSemenov]

Same here, I ended up selecting "What CI are you using? Other (prints tokens)" and setting up the tokens at Travis manually.

(I found this actually making more sense as I can now have a single token reused for many Travis CI projects.)

[CalmJerome]

Same here!

[gr2m]

likely same issue as discussed in https://github.com/semantic-release/cli/issues/345

[prantlf]

It appears, that the support for GitHub tokens instead of user credentials is not finished yet.

semantic-release-cli setup --gh-token=a...z --npm-token=a...f
? What is your npm registry? https://registry.npmjs.org/
? What CI are you using? Travis CI
ERR! semantic-release no access token supplied

What token is semantic-release complaining about?

[ashblue]

I'm also getting ERR! semantic-release no access token supplied even though I provided a token. The current fix doesn't work it seems. Any ETA on a fix?

[gitofdeepanshu]

Any update on the situation?

[smshareef026]

Any fix for the issue?

[matzar]

@smshareef026 if you haven't already and this wasn't just a testing token, I'd recommend deleting this screenshot showing your GitHub Personal Access Token.

[AhHa45]

any update on this?

[prantlf]

A workaround not for everybody, but might help somebody - retain the semantic-release package family, but avoid the semantic-release-cli package.

1. Migrate your CI/CD pipeline to GitHub Actions
2. Publish your NPM module using Semantic Release Action