Skip to content

How to target setup NODE version using environmental variables without hitting runner itself? #356

Closed
@jkabat

Description

@jkabat

Description:
Im trying to add Node v17 into the matrix but because of known openssl bug I need to set "--openssl-legacy-provider" in NODE_OPTIONS. Using actions environment variables seems to be affected even runner which is not very recent and fails on unrecognizable option. Is there something I can do about it?

Action version:
Latest.

Platform:

  • Ubuntu
  • macOS
  • Windows

Runner type:

  • Hosted
  • Self-hosted

Repro steps:

  - name: Setup NODE
    uses: actions/setup-node@v1
    with:
          node-version: "17"
    env:
          NODE_OPTIONS: "--openssl-legacy-provider"

Expected behavior:
Step will end up without an error.

Actual behavior:
Step fails with:

Run actions/setup-node@v2.4.1
/home/runner/runners/2.283.3/externals/node12/bin/node: --openssl-legacy-provider is not allowed in NODE_OPTIONS```

Metadata

Metadata

Labels

bugSomething isn't working

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions