-
Notifications
You must be signed in to change notification settings - Fork 7
GH_TOKEN has not authenticated Travis CI yet #52
Comments
I see from the logs that the module try to access This is something we should improve in the setup cli. |
Thanks! 🎊 Simply adding "scripts": {
"travis-deploy-once": "travis-deploy-once --pro"
} |
I've had the same issue, although for free-tier version. I think it's probably because of the new |
I'm having this issue if I specify "Travis CI (Pro)" in the CI selection for cli and it fails with a file not found error, and I then attempt with "Other" and add my keys manually on travis-ci.com |
Strange that adding the |
To solve this issue: semantic-release/travis-deploy-once#52
To solve this issue: semantic-release/travis-deploy-once#52
## [2.3.1](v2.3.0...v2.3.1) (2018-11-22) ### Bug Fixes * **travis:** 🐛 use --pro flag for travis-deploy-once ([52f8b7d](52f8b7d)), closes [semantic-release/travis-deploy-once#52](semantic-release/travis-deploy-once#52)
I'm experiencing #13 with travis-deploy-once@4.3.3. I've initialised a semantic-release@12.2.4 project with
npx semantic-release-cli setup
, but the Travis jobs fail with:I have tried logging in as the GitHub user who owns
GH_TOKEN
on Travis and have tried manually generating a GitHub personal access token with repo scope (it's a private repo).Current workaround is to pin to semantic-release@7.0.2.
Full error
The text was updated successfully, but these errors were encountered: