Repository navigation
Don't set UV_CACHE_DIR if enable-cache is false #583
Description
When the UV_CACHE_DIR environment variable is set, it takes precidence over the project-specific setting tool.uv.cache-dir. This makes it imossible to use this setup action when requiring custom cache configuration on a per-project basis. This is probably a niche requirement, but I'm personally using it while testing another tool's ability to correctly save and restore UV caches.
My expectation would be that explicitly disabling the cache by setting enable-cache: false would avoid setting this environment variable, but this is not the case as it's set unconditionally in the run function:
Line 57 in 208b0c0
It's currently not possible to unset an environment variable in GitHub actions (see: actions/runner#1126) so I don't think there's a workaround to allow projects to use their own cache directories.
Activity
eifinger commentedon Sep 22, 2025
We could add the functionality to look for configurations in the config files and only then apply defaults.
Until then, as a workaround, can you use the
cache-local-pathinput?danielrbradley commentedon Sep 22, 2025
I don't think that'll work for us as it needs to be a different location for each test.
I assume we can't just unset
UV_CACHE_DIRas that might be a breaking change for existing users even if they're not using the cache themselves?eifinger commentedon Sep 22, 2025
If you set
enable-cache: falsethen you can do whatever you want withUV_CACHE_DIRas this action won'trely onuse it thenRespect UV_CACHE_DIR and cache-dir (#612)