# "missing token" on attempt to deploy to Github releases

**URL:** <https://travis-ci.community/t/missing-token-on-attempt-to-deploy-to-github-releases/10424>\
**Category:** Deployment\
**Created:** [November 2, 2020, 6:23pm UTC](https://travis-ci.community/t/missing-token-on-attempt-to-deploy-to-github-releases/10424 "2020-11-02T18:23:22Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![neilyoung](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/neilyoung/32/5468_2.png) [@neilyoung](https://travis-ci.community/u/neilyoung)\
**Post date:** [November 2, 2020, 6:23pm UTC](https://travis-ci.community/t/missing-token-on-attempt-to-deploy-to-github-releases/10424/1 "2020-11-02T18:23:22Z")

</div>

I’m wrestling with Travis (great tool btw), making an attempt to deploy to Github releases.

I basically was following this tutorial [https://dev.to/hawkinjs/leveraging-travis-ci-for-continuous-deployment-to-publish-compiled-binaries-to-github-2k06](https://dev.to/hawkinjs/leveraging-travis-ci-for-continuous-deployment-to-publish-compiled-binaries-to-github-2k06)

From the Travis dashboard I see, that build and test was OK for all targets. But Travis has some problems with my .travis.yml. There is this “unknown key api\_token”, which concerns me:

 ![image](https://us1.discourse-cdn.com/flex015/uploads/travis_ci/original/2X/6/6fec8884087c57363eb6c32c263df0d632890d8d.png)

According to the tutorial and some other sources I saw, this is the proper way to configure the github token, or is it not?

```
deploy:
  - provider: releases
    skip_cleanup: true
    on:
      tags: true
      condition: "$TRAVIS_RUST_VERSION = stable"
      branch: master
    file: target/release/camtest
    api_token:
      secure: "my_secret_token_obtained_from_travis_encrypt"

```

Regards

---

<div class="post-metadata">

**Author:** ![native-api](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/native-api/32/430_2.png) [@native-api](https://travis-ci.community/u/native-api)\
**Post date:** [November 11, 2020, 12:55pm UTC](https://travis-ci.community/t/missing-token-on-attempt-to-deploy-to-github-releases/10424/2 "2020-11-11T12:55:02Z")

</div>

We cannot vouch for accuracy and up-to-dateness of 3rd-party tutorials.

The official documentation on deployment to Github Releases is:

> **[Travis CI Documentation](https://docs.travis-ci.com/user/deployment/releases/)**
>
> GitHub Releases Uploading

The thing that gives users the most trouble with Github Releases deployment is that Github requires the commit associated with a Releases deployment to be tagged. Keep this fact in mind when reading the documentation.

---

<div class="post-metadata">

**Author:** ![neilyoung](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/neilyoung/32/5468_2.png) [@neilyoung](https://travis-ci.community/u/neilyoung)\
**Post date:** [November 11, 2020, 1:27pm UTC](https://travis-ci.community/t/missing-token-on-attempt-to-deploy-to-github-releases/10424/3 "2020-11-11T13:27:35Z")

</div>

Yes, thanks. I totally forgot about this. Meanwhile I have dropped Travis in favour of Github actions.