System.ArgumentOutOfRangeException using: node20' is not supported

[neseleznev]

Describe the bug

After upgrading to v4, we have the exception from time to time

Expected Behavior

I expect it to work.
We have 15 similar jobs in the workflow which run in parallel.
Sometimes, one of them fails with the exception.
A retry helps

Current Behavior

Error: System.ArgumentOutOfRangeException: Specified argument was out of the range of valid values. (Parameter ''using: node20' is not supported, use 'docker', 'node12' or 'node16' instead.')
   at GitHub.Runner.Worker.ActionManifestManager.ConvertRuns(IExecutionContext executionContext, TemplateContext templateContext, TemplateToken inputsToken, String fileRelativePath, MappingToken outputs)
   at GitHub.Runner.Worker.ActionManifestManager.Load(IExecutionContext executionContext, String manifestFile)
Error: Fail to load aws-actions/configure-aws-credentials/v4/action.yml

Reproduction Steps

    - name: Configure AWS credentials
      uses: aws-actions/configure-aws-credentials@v4
      with:
        aws-region: ***
        role-to-assume: ***

Possible Solution

No response

Additional Information/Context

No response

[peterwoodworth]

What runner are you using in the cases that it fails?

[neseleznev]

What runner are you using in the cases that it fails?

It's self-hosted if this matters. JFYI, there are 15 parallel jobs in the same configuration, which run in parallel

P.S. the error happens on the Set up job step:

Download action repository 'aws-actions/configure-aws-credentials@v4' (SHA:010d0da01d0b5a38af31e9c3470dbfdabdecca3a)
Download action repository 'aws-actions/amazon-ecr-login@v1' (SHA:2fc7aceee09e9e4a7105c0d060c656fad0b4f63d)
Error: System.ArgumentOutOfRangeException: Specified argument was out of the range of valid values. (Parameter ''using: node20' is not supported, use 'docker', 'node12' or 'node16' instead.')
   at GitHub.Runner.Worker.ActionManifestManager.ConvertRuns(IExecutionContext executionContext, TemplateContext templateContext, TemplateToken inputsToken, String fileRelativePath, MappingToken outputs)
   at GitHub.Runner.Worker.ActionManifestManager.Load(IExecutionContext executionContext, String manifestFile)
Error: Fail to load aws-actions/configure-aws-credentials/v4/action.yml

[peterwoodworth]

As far as I'm aware, GitHub self hosted runners should update automatically. So I doubt that it's your runner version being out of date, but I'm also not sure why else this would be occurring since node20 is a valid value - else it would be failing every time. Very strange that this error is occurring intermittently with the same runner

[tim-finnigan]

How often does this issue occur? Can you share any steps for consistently reproducing it?

[neseleznev]

How often does this issue occur? Can you share any steps for consistently reproducing it?

From what I faced, it had happened 4 times in the past few weeks (since the action version upgrade).
I have no steps to reproduce it

[AkshataHegde-ZS]

We are also facing the same issue with the aws-actions/configure-aws-credentials@v4 in windows self-hosted runner. For us, the issue is not intermittent, but happening with every time the action runs.

[tim-finnigan]

Node20 support was added in actions/[email protected] (See commit here). For self hosted runners, you will have to update your runner code. If you’re running on GitHub, that may indicate a bug in GitHub. If the issue occurs intermittently, we'd need to figure out if it’s the runner version that’s the problem. Runner versions are reported in the “Set Up Job” step of every workflow execution.

[neseleznev]

Node20 support was added in actions/[email protected]

I checked the failed runner. Indeed, it had an older version than the required

Current runner version: '2.299.1'

Thank you!

[neseleznev]

Considering that this is not obvious, you may want to add a word in the v4 announcement about the minimal actions/runner version required

[github-actions]

Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.