# "missing api\_key" when deploying to GitHub releases **URL:** \ **Category:** Deployment\ **Created:** [November 3, 2019, 10:39am UTC](https://travis-ci.community/t/missing-api-key-when-deploying-to-github-releases/5761 "2019-11-03T10:39:06Z")\ **Posts on this page:** 1\ **Showing post:** 14
**Author:** ![svenfuchs](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/svenfuchs/32/2570_2.png) [@svenfuchs](https://travis-ci.community/u/svenfuchs)\ **Post date:** [November 19, 2019, 9:01pm UTC](https://travis-ci.community/t/missing-api-key-when-deploying-to-github-releases/5761/14 "2019-11-19T21:01:56Z")
Sorry about this issue everyone. This is indeed an incompatibility of the feature Build Config Validation with the beta version `v2` of our deployment tooling `dpl` which is not used by default, yet. Build Config Validation applies a formal schema to your build configuration that specifies things as required for `dpl v2`, but not `dpl v1` even though this is still the standard version (if everything goes to plan this default will be switched in Jan). This is an oversight on our part in coordinating these two non-trivial releases. We are working on ways to reduce these issues. In the meantime you can resolve this by opting into `v2` using: ```auto deploy: - provider: [name] edge: true ``` --- _[View the full topic](https://travis-ci.community/t/missing-api-key-when-deploying-to-github-releases/5761)._