Failure on self-hosted runners using Node 18 - ReferenceError: File is not defined

[my1e5]

v6.6.0 is failing at the set up stage for me. Using v6.5.0 works fine. I'm using a self-hosted runner with Gitea.

v6.6.0

    - name: Set up uv
      id: setup-uv
      uses: astral-sh/setup-uv@v6.6.0
      with:
        enable-cache: true
        prune-cache: false
        version: 0.8.8
        python-version: ${{ matrix.python-version }}

These are the logs I'm currently able to get:

/run/act/actions/91a3cdd30079ddbfaf6f1ef1a5a84e50cfd0ec07e82e0de5aee5da2ba2e77383/dist/setup/index.js:113176
webidl.is.File = webidl.util.MakeTypeAssertion(File)
                                               ^
ReferenceError: File is not defined
    at 47879 (/run/act/actions/91a3cdd30079ddbfaf6f1ef1a5a84e50cfd0ec07e82e0de5aee5da2ba2e77383/dist/setup/index.js:113176:48)
    at __nccwpck_require__ (/run/act/actions/91a3cdd30079ddbfaf6f1ef1a5a84e50cfd0ec07e82e0de5aee5da2ba2e77383/dist/setup/index.js:135576:43)
    at 73168 (/run/act/actions/91a3cdd30079ddbfaf6f1ef1a5a84e50cfd0ec07e82e0de5aee5da2ba2e77383/dist/setup/index.js:110888:20)
    at __nccwpck_require__ (/run/act/actions/91a3cdd30079ddbfaf6f1ef1a5a84e50cfd0ec07e82e0de5aee5da2ba2e77383/dist/setup/index.js:135576:43)
    at 60660 (/run/act/actions/91a3cdd30079ddbfaf6f1ef1a5a84e50cfd0ec07e82e0de5aee5da2ba2e77383/dist/setup/index.js:106127:5)
    at __nccwpck_require__ (/run/act/actions/91a3cdd30079ddbfaf6f1ef1a5a84e50cfd0ec07e82e0de5aee5da2ba2e77383/dist/setup/index.js:135576:43)
    at 99051 (/run/act/actions/91a3cdd30079ddbfaf6f1ef1a5a84e50cfd0ec07e82e0de5aee5da2ba2e77383/dist/setup/index.js:110229:90)
    at __nccwpck_require__ (/run/act/actions/91a3cdd30079ddbfaf6f1ef1a5a84e50cfd0ec07e82e0de5aee5da2ba2e77383/dist/setup/index.js:135576:43)
    at 54398 (/run/act/actions/91a3cdd30079ddbfaf6f1ef1a5a84e50cfd0ec07e82e0de5aee5da2ba2e77383/dist/setup/index.js:106855:5)
    at __nccwpck_require__ (/run/act/actions/91a3cdd30079ddbfaf6f1ef1a5a84e50cfd0ec07e82e0de5aee5da2ba2e77383/dist/setup/index.js:135576:43)
Node.js v18.20.8
  ❌  Failure - Main Set up uv
exitcode '1': failure

v6.5.0

This is working fine.

    - name: Set up uv
      id: setup-uv
      uses: astral-sh/setup-uv@v6.5.0
      with:
        enable-cache: true
        prune-cache: false
        version: 0.8.8
        python-version: ${{ matrix.python-version }}

Found uv in tool-cache for 0.8.8
Added /root/.local/bin to the path
Added /opt/hostedtoolcache/uv/0.8.8/x86_64 to the path
Set UV_PYTHON to 3.12
##[add-matcher]/run/act/actions/d0bdefcf7c722ab5e931bbbe5c993190056e688a4e97062d7aaa8f1205a02403/.github/python.json
Set UV_CACHE_DIR to /root/.cache/uv
Successfully installed uv version 0.8.8
Searching files using cache dependency glob: /workspace/Research/Python/**/*requirements*.txt,/workspace/Research/Python/**/*requirements*.in,/workspace/Research/Python/**/*constraints*.txt,/workspace/Research/Python/**/*constraints*.in,/workspace/Research/Python/**/pyproject.toml,/workspace/Research/Python/**/uv.lock
/workspace/Research/Python/pyproject.toml
/workspace/Research/Python/uv.lock
Found 2 files to hash.
Trying to restore uv cache from GitHub Actions cache with key: setup-uv-1-x86_64-unknown-linux-gnu-3.12-1944992fedef2dc52b49cc0a7fd4d148b7822103bf9032ddb497d83ffa35ef39
Cache Size: ~120 MB (126345583 B)
[command]/usr/bin/tar -xf /tmp/dd1aaf22-d897-4efb-b736-15022cee3f9e/cache.tzst -P -C /workspace/Research/Python --use-compress-program unzstd
Cache restored successfully
uv cache restored from GitHub Actions cache with key: setup-uv-1-x86_64-unknown-linux-gnu-3.12-1944992fedef2dc52b49cc0a7fd4d148b7822103bf9032ddb497d83ffa35ef39

[eifinger]

Is this running on a selfhosted runner? I see node18 mentioned. The lowest supported version for GitHub Action runners is 20 afaik

[gvacaliuc]

Noticed this when using https://github.com/nektos/act w/ ubuntu-latest set as the runner.

Reproduction w/ minimal workflow: https://github.com/gvacaliuc/setup-uv-535. Interesting that the workflow succeeds on github!

[Zaephor]

Just bit me too, identical error with node18.

Using Gitea selfhosted runners, which generally use the ghcr.io/catthehacker/ubuntu:act-* images or mirrors of them. Doesn't seem like they've bumped the nodejs version in a while, nor what -latest points to.

According to catthehacker/docker_images#139 a migration was planned/started to migrate them to a new namespace, so maybe the projects been a tad stale while they work through it.

[abrain]

Gitea has released a new runner, that allows running node24: https://gitea.com/gitea/act_runner/releases/tag/v0.2.13

It works with the actions/checkout v5 action, which previously failed as well as it requires node24. But the uv Action v6.6.1 still fails (mentioning Node 18 as above).

[my1e5]

Gitea has released a new runner, that allows running node24: gitea.com/gitea/act_runner/releases/tag/v0.2.13
It works with the actions/checkout v5 action, which previously failed as well as it requires node24.

From what I understand, actions/checkout@v5 still works with older node versions (including 18). It's just that they added support for Node 24. This meant they now supported a node24 tag which act_runner didn't recognise as a valid option.

The popular actions/checkout action released version v5.0.0 a few hours ago, and it has a compatibility issue with the gitea act_runner. When updating my workflows to use this action (via renovate), the build fails in the "Set up job" step with the error:

The runs.using key in action.yml must be one of: [composite docker node12 node16 node20 go], got node24

(from actions/checkout v5 action dies with a "node24" error #729)

As you point out, this is now fixed in the v0.2.13 release. So act_runner doesn't error anymore when it encounters node24.

But the uv Action v6.6.1 still fails (mentioning Node 18 as above).

I've spoken to some of the Gitea devs, and the problem is exactly what @Zaephor said:

Using Gitea selfhosted runners, which generally use the ghcr.io/catthehacker/ubuntu:act-* images or mirrors of them. Doesn't seem like they've bumped the nodejs version in a while, nor what -latest points to.

Node 20 is not included in the image. You can see the Node versions listed here - https://github.com/catthehacker/docker_images/blob/7df48ceacddf5c162cd6b1cbae4972e14c5bdfd7/linux/ubuntu/Dockerfile#L14

They've said that the catthehacker images are planned for deprecation and everything moved to https://github.com/actions-oss/act-docker-images. So eventually we should have new images with Node 20 included by default.

Until then, one simple workaround is to add Node 20 ourselves before running setup-uv. e.g.

- name: Set up Node.js
  uses: actions/setup-node@v4
  with:
    node-version: 20
- name: Set up uv
  uses: astral-sh/setup-uv@v6

[abrain]

Ah, thanks for the clarification! Makes more sense now.

Tried out the workaround, and it works. Thanks for that as well!

[eifinger]

Release v7.0.0 uses node24. You might not need the workaround anymore

[SecT0uch]

Just tried with:

jobs:
  jobname:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v5

      - name: Install uv
        uses: astral-sh/setup-uv@v7

And still getting:

/run/act/actions/c2db993cd5075e9cd1ff620c7087b7face2d6ae7787eb466688b0d780bc569b0/dist/setup/index.js:114401
webidl.is.File = webidl.util.MakeTypeAssertion(File)
                                               ^
ReferenceError: File is not defined
    at 47879 (/run/act/actions/c2db993cd5075e9cd1ff620c7087b7face2d6ae7787eb466688b0d780bc569b0/dist/setup/index.js:114401:48)
    at __nccwpck_require__ (/run/act/actions/c2db993cd5075e9cd1ff620c7087b7face2d6ae7787eb466688b0d780bc569b0/dist/setup/index.js:137257:43)
    at 73168 (/run/act/actions/c2db993cd5075e9cd1ff620c7087b7face2d6ae7787eb466688b0d780bc569b0/dist/setup/index.js:112002:20)
    at __nccwpck_require__ (/run/act/actions/c2db993cd5075e9cd1ff620c7087b7face2d6ae7787eb466688b0d780bc569b0/dist/setup/index.js:137257:43)
    at 60660 (/run/act/actions/c2db993cd5075e9cd1ff620c7087b7face2d6ae7787eb466688b0d780bc569b0/dist/setup/index.js:107244:5)
    at __nccwpck_require__ (/run/act/actions/c2db993cd5075e9cd1ff620c7087b7face2d6ae7787eb466688b0d780bc569b0/dist/setup/index.js:137257:43)
    at 99051 (/run/act/actions/c2db993cd5075e9cd1ff620c7087b7face2d6ae7787eb466688b0d780bc569b0/dist/setup/index.js:111345:90)
    at __nccwpck_require__ (/run/act/actions/c2db993cd5075e9cd1ff620c7087b7face2d6ae7787eb466688b0d780bc569b0/dist/setup/index.js:137257:43)
    at 54398 (/run/act/actions/c2db993cd5075e9cd1ff620c7087b7face2d6ae7787eb466688b0d780bc569b0/dist/setup/index.js:107972:5)
    at __nccwpck_require__ (/run/act/actions/c2db993cd5075e9cd1ff620c7087b7face2d6ae7787eb466688b0d780bc569b0/dist/setup/index.js:137257:43)
Node.js v18.20.8
  ❌  Failure - Main Install uv
exitcode '1': failure

[my1e5]

Release v7.0.0 uses node24. You might not need the workaround anymore

Thanks for the update. I just tested out v7 and it looks like we still need Node 20 at a minimum. So the workaround is still needed until the docker images we rely on are updated.

[DhavalGojiya]

Release v7.0.0 uses node24. You might not need the workaround anymore

Not working with astral-sh/setup-uv@v7 as well.