no access token supplied about cli HOT 10 OPEN

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.)

from cli.

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?

from cli.

Any fix for the issue?

from cli.

@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.

from cli.

Same here!

from cli.

likely same issue as discussed in #345

from cli.

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?

from cli.

Any update on the situation?

from cli.

any update on this?

from cli.

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

from cli.