I couldn't find a VERCEL TOKEN environment

[sujamess]

Workflow

steps:
  # Waiting for Vercel deployment
  - uses: UnlyEd/[email protected]
    id: await-vercel
    env:
      VERCEL_TOKEN: ${{ secrets.VERCEL_TOKEN }}
    with:
      deployment-url: ${{ secrets.VERCEL_DEPLOYMENT_URL }}
      timeout: 10 # Wait for 10 seconds before failing

Error

Run UnlyEd/[email protected]
Error: VERCEL_TOKEN environment variable is not defined. Please create a GitHub "VERCEL_TOKEN" secret. See https://vercel.com/account/tokens
/home/runner/work/_actions/UnlyEd/github-action-await-vercel/v1.1.0/lib/main.js:38
        throw new Error(message);
        ^

Error: VERCEL_TOKEN environment variable is not defined. Please create a GitHub "VERCEL_TOKEN" secret. See https://vercel.com/account/tokens
    at runConfigChecks (/home/runner/work/_actions/UnlyEd/github-action-await-vercel/v1.1.0/lib/main.js:38:15)
    at Object.<anonymous> (/home/runner/work/_actions/UnlyEd/github-action-await-vercel/v1.1.0/lib/main.js:65:1)
    at Module._compile (internal/modules/cjs/loader.js:959:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:995:10)
    at Module.load (internal/modules/cjs/loader.js:815:32)
    at Function.Module._load (internal/modules/cjs/loader.js:727:14)
    at Function.Module.runMain (internal/modules/cjs/loader.js:1047:10)
    at internal/main/run_main_module.js:17:11

I already created a VERCEL_TOKEN secret and I also see this error on UnlyEd/github-action-await-vercel with a dependabot's pull requests

[Vadorequest]

Regarding the configuration of https://github.com/UnlyEd/github-action-await-vercel, a VERCEL_TOKEN is configured, though.

Looking back at the logs of the actions, it seems that it failed to retrieve the token in the past, too. But it also worked 15 days ago...

https://github.com/UnlyEd/github-action-await-vercel/actions

I'm not sure why you encountered this issue. It seems a bit random at first look. 🤔

[Vadorequest]

Okay, the reason why the VERCEL_TOKEN was empty and why the actions failed at https://github.com/UnlyEd/github-action-await-vercel/actions is because the workflow was triggered by a 3rd party, which doesn't have read access to our repository GitHub's secrets.

See https://stackoverflow.com/a/58740879/2391795 for deeper explanations.

And the reason sometimes it worked, was because those runs were triggered by our own PRs, which have read access to the GitHub's secrets.

Now, why did it fail for you is another issue, I believe you should log your VERCEL_TOKEN to see if it contains the expected value.

[Vadorequest]

I suggest trying using 1.2.14 version. And if you can provide your full action's code too, that might be helpful.

[sujamess]

I use your actions for auto-merging the dependabot pull requests. This is the full actions code.

name: Dependabot Auto Merge

on:
  pull_request:
  workflow_dispatch:

jobs:
  dependabot-auto-merge:
    runs-on: ubuntu-18.04
    if: |
      github.actor == 'dependabot[bot]' &&
      github.event_name == 'pull_request' &&
      startsWith(github.event.pull_request.title, 'Bump')
    steps:
      # Waiting for Vercel deployment
      - uses: UnlyEd/[email protected]
        id: await-vercel
        env:
          VERCEL_TOKEN: ${{ secrets.VERCEL_TOKEN }}
        with:
          deployment-url: ${{ secrets.VERCEL_DEPLOYMENT_URL }}
          timeout: 10 # Wait for 10 seconds before failing

      - name: Display deployment status
        run: "echo The deployment at ${{ fromJson(steps.await-vercel.outputs.deploymentDetails).url }} is ${{ fromJson(steps.await-vercel.outputs.deploymentDetails).readyState }}"
      
      # Auto merge dependabot
      - uses: actions/checkout@v2
      - uses: ahmadnassri/action-dependabot-auto-merge@v2
        with:
          github-token: ${{ secrets.TOKEN }}

[sujamess]

Thank you for the suggestion. I'll try with v1.2.14 🙏🏻

[Vadorequest]

Unrelated, but github-token: ${{ secrets.TOKEN }} shouldn't it be github-token: ${{ secrets.GITHUB_TOKEN }} instead?

[sujamess]

From the naming rules here:

Secret names must not start with the GITHUB_ prefix.

And it failed from the first step (await-vercel) so I think it's not related

[Vadorequest]

Yeah, but there is a special GITHUB_TOKEN you can use.

https://docs.github.com/en/actions/security-guides/automatic-token-authentication#about-the-github_token-secret

[sujamess]

It still occurs with v1.2.14

Run UnlyEd/[email protected]
Error: VERCEL_TOKEN environment variable is not defined. Please create a GitHub "VERCEL_TOKEN" secret. See https://vercel.com/account/tokens

/home/runner/work/_actions/UnlyEd/github-action-await-vercel/v1.2.14/webpack:/github-action-await-vercel/lib/main.js:45
    if (!core.isDebug()) {
^
Error: VERCEL_TOKEN environment variable is not defined. Please create a GitHub "VERCEL_TOKEN" secret. See https://vercel.com/account/tokens
    at run (/home/runner/work/_actions/UnlyEd/github-action-await-vercel/v1.2.14/webpack:/github-action-await-vercel/lib/main.js:45:1)
    at Object.__webpack_require__ (/home/runner/work/_actions/UnlyEd/github-action-await-vercel/v1.2.14/webpack:/github-action-await-vercel/lib/main.js:66:1)
    at __nccwpck_require__ (/home/runner/work/_actions/UnlyEd/github-action-await-vercel/v1.2.14/webpack:/github-action-await-vercel/webpack/bootstrap:21:1)
    at /home/runner/work/_actions/UnlyEd/github-action-await-vercel/v1.2.14/webpack:/github-action-await-vercel/webpack/startup:4:1
    at Object.<anonymous> (/home/runner/work/_actions/UnlyEd/github-action-await-vercel/v1.2.14/webpack:/github-action-await-vercel/webpack/startup:4:1)
    at Module._compile (internal/modules/cjs/loader.js:959:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:995:10)
    at Module.load (internal/modules/cjs/loader.js:815:32)
    at Function.Module._load (internal/modules/cjs/loader.js:727:14)
    at Function.Module.runMain (internal/modules/cjs/loader.js:1047:10)

IIRC, it does not trigger by the 3rd party. So, any suggestions? Or it's an actions limitation?

[Vadorequest]

Yeah, I really didn't expect it to be fixed by using another version, but it's better to try using the latest anyway.

If you print your VERCEL_TOKEN in your logs, does it show the expected value?