Setting FORCE_COLOR=true does not seem to work (in GH actions at least)

[scop]

Setting FORCE_COLOR=true does not seem to give colorized output in GitHub actions.

Reproducer pipeline job at https://github.com/scop/pytekukko/actions/runs/12620953794/job/35167229162 (the "Install Python dev dependencies" step)

• Shows that FORCE_COLOR is set to true in the env, and there's no NO_COLOR or CLICOLOR_FORCE env vars present
• Shows that there's no --color arg passed to uv

...but the uv output has no color. I tried explicit export of FORCE_COLOR too, to no avail.

Another job at https://github.com/scop/pytekukko/actions/runs/12620965743/job/35167258389 that passes --color always does result in color output (again, see the "Install Python dev dependencies" step).

This workflow uses the current astral-sh/setup-uv action, so uv is current, too.

[samypr100]

Can you give CLICOLOR_FORCE="true" instead a quick try?

[samypr100]

Here's an isolated MRE

Works

docker run --platform linux/x86_64 -e CLICOLOR_FORCE=1 --rm ghcr.io/astral-sh/uv:python3.12-alpine /bin/sh -c "uv init test"

Does not work

docker run --platform linux/x86_64 -e FORCE_COLOR=1 --rm ghcr.io/astral-sh/uv:python3.12-alpine /bin/sh -c "uv init test"

Seems like this stopped working after 0.5.0, possibly related to #8215

Works

docker run --platform linux/x86_64 -e FORCE_COLOR=1 --rm ghcr.io/astral-sh/uv:0.4.30-python3.12-alpine /bin/sh -c "uv init test"
docker run --platform linux/x86_64 -e CLICOLOR_FORCE=1 --rm ghcr.io/astral-sh/uv:0.4.30-python3.12-alpine /bin/sh -c "uv init test"
docker run --platform linux/x86_64 -e CLICOLOR_FORCE=1 --rm ghcr.io/astral-sh/uv:0.5.0-python3.12-alpine /bin/sh -c "uv init test"

Does not work

docker run --platform linux/x86_64 -e FORCE_COLOR=1 --rm ghcr.io/astral-sh/uv:0.5.0-python3.12-alpine /bin/sh -c "uv init test"

[charliermarsh]

Thanks @samypr100!

[charliermarsh]

Fixed in #10315.