You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The documentation does not mention anything about my problem
There are no open or closed issues that are related to my problem
Description
A recent commit (02e9319) switched the runner version for the action to node20 from node16. On our self-hosted Github Enterprise server, this results in actions failing with the error.
Expected behaviour
Ideally, a change to the runner to a newer version that is possibly unsupported everywhere would be tagged with a new label (e.g. no longer v3.0.0) so we could continue to use the supported version.
Actual behaviour
Our actions are failing with an error:
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 docker/setup-buildx-action/v3/action.yml
So this may have been filed a little prematurely: we updated our Github actions runner image from v2.306.0-ubuntu-20.04 to v2.309.0-ubuntu-20.04 and node20 is accepted now.
Contributing guidelines
I've found a bug, and:
Description
A recent commit (02e9319) switched the runner version for the action to
node20
fromnode16
. On our self-hosted Github Enterprise server, this results in actions failing with the error.Expected behaviour
Ideally, a change to the runner to a newer version that is possibly unsupported everywhere would be tagged with a new label (e.g. no longer
v3.0.0
) so we could continue to use the supported version.Actual behaviour
Our actions are failing with an error:
Repository URL
No response
Workflow run URL
No response
YAML workflow
Workflow logs
No response
BuildKit logs
No response
Additional info
No response
The text was updated successfully, but these errors were encountered: