Hello,
we're using this action on our self-hosted on-premise runners. Unfortunately, they are behind a corporate proxy, which sometimes does deep packet inspection and uses a self-signed certificate (unless it's a well known URL like from GitHub). This manifests in the following warnings:
Trying to find version for uv in: /home/runner/_work/ia-releases/ia-releases/uv.toml
Could not find file: /home/runner/_work/ia-releases/ia-releases/uv.toml
Trying to find version for uv in: /home/runner/_work/ia-releases/ia-releases/pyproject.toml
Could not find file: /home/runner/_work/ia-releases/ia-releases/pyproject.toml
Could not determine uv version from uv.toml or pyproject.toml. Falling back to latest.
Fetching manifest data from https://raw.githubusercontent.com/astral-sh/versions/main/v1/uv.ndjson ...
Downloading uv from "https://releases.astral.sh/github/uv/releases/download/0.11.8/uv-x86_64-unknown-linux-gnu.tar.gz" ...
self-signed certificate in certificate chain
Waiting 20 seconds before trying again
self-signed certificate in certificate chain
Waiting 13 seconds before trying again
Warning: Failed to download from mirror, falling back to GitHub Releases: self-signed certificate in certificate chain
Downloading uv from "https://github.com/astral-sh/uv/releases/download/0.11.8/uv-x86_64-unknown-linux-gnu.tar.gz" ...
/usr/bin/tar xz --warning=no-unknown-keyword --overwrite -C /home/runner/_work/_temp/e6a64d89-f6b6-483b-ba0b-07763b22fe41 -f /home/runner/_work/_temp/4f2cc7fa-4d40-49ae-a545-8fec128cb227
Added /home/runner/.local/bin to the path
Added /home/runner/_work/_tool/uv/0.11.8/x86_64 to the path
Set UV_PYTHON_INSTALL_DIR to /home/runner/.local/share/uv/python
Added /home/runner/.local/share/uv/python to the path
Successfully installed uv version 0.11.8
As you can see, it delays the setup by ~30 seconds and then falls back to the GitHub releases anyway.
Could you please add an input parameter to explicitly choose the GitHub option? Or maybe handle self-signed certificates better because they won't suddenly be resolved if you try again or wait longer.
Hello,
we're using this action on our self-hosted on-premise runners. Unfortunately, they are behind a corporate proxy, which sometimes does deep packet inspection and uses a self-signed certificate (unless it's a well known URL like from GitHub). This manifests in the following warnings:
As you can see, it delays the setup by ~30 seconds and then falls back to the GitHub releases anyway.
Could you please add an input parameter to explicitly choose the GitHub option? Or maybe handle self-signed certificates better because they won't suddenly be resolved if you try again or wait longer.