this is my build history and .travis.yml config: https://travis-ci.org/DWmister/build-pack/jobs/629531172/config Also, I don’t know why this happens?, use v1 ‘api_key’ ----- ‘api_token’ In addition, I also used the v2. In v2, I know ‘api_token’ alias: ‘api_key’,but,Same problem as above https:…

npm: port alias from travis-yml and dpl v2 travis-ci:v1 ← native-api:npm_v2_alias opened 03:02PM - 26 Dec 19 UTC (UTC) [native-api] native-api …

I’m having the same issue, but on https://travis-ci.com , my steps: gem install travis cd my-project-name travis login --pro (needed for .com projects?) travis encrypt my-api-key --com Pasted resulting key in my .travis.yml language: node_js node_js: - '12' # EOL: April 2022 - '10' # EOL…

Disabling build config validation in repository settings is not getting around this issue for me

@jesslynlandgren Can’t say anything without seeing a build. I guess you are having some unrelated problem – e.g. envvars not set.

i had the same issue… NOTE: once you disable build config validation, you must create a new build, restarting your previously failed build wont work.

I’m also seeing this issue. We haven’t changed anything related to build config, and environment variables, and NPM deploy suddenly stopped working several days ago. Here’s a failing build: https://travis-ci.org/LLK/scratch-paint/jobs/642625925 Here’s our source repo: LLK/scratch-paint/b…

We have now had to turn off build verification for most of our repos because of this issue

@BanzaiMan AFAICS the fix is not yet a part of a release – so users keep seeing this issue. There are a bunch of other active PRs against v1 if you think that one fix is too little for a release :wink:

I haven’t change anything from Travis deploy config but suddenly it stopped working because of missing api_key hamidfzm/ra-language-farsi/blob/master/.travis.yml language: node_js script: 'true' deploy: provider: npm email: contact@hamidfzm.ir api_key: secure: ITyX6otJh0tI8+T150x…

@hamidfzm [image] When configuration validation is on, environment variable definition order may change Linux We are rolling out the configuration validator to more and more repositories.

[image] alewitt2: NOTE: once you disable build config validation, you must create a new build, restarting your previously failed build wont work. You should pin this somewhere. My production deployments suddenly stopped working thanks to randomly being opted in to a beta.

Npm deploy failed && missing api_key, but I have set it

Deployment

capaj February 13, 2020, 8:55am 14

it helped in my case for https://travis-ci.org/capaj/decapi

Topic		Replies	Views
Build Config Validation: Using `api_key` breaks npm deployments Build Config Validation config-validation	4	6523	February 24, 2020
NPM deploy fails always on travis-ci.com Deployment	1	988	March 22, 2020
"missing api_key" when deploying to GitHub releases Deployment	15	6446	February 20, 2020
Cannot publish NPM package: env: ‘to’: No such file or directory Node.js	5	3095	November 11, 2019
No stash entries found. missing api_key failed to deploy Deployment	3	7661	February 26, 2023

Npm deploy failed && missing api_key, but I have set it

Related topics