Cache service responded with 422

[carlosmiei]

Description:
Hello guys :)

We have been using this action extensively in our repo: https://github.com/ccxt/ccxt/blob/master/.github/workflows/python.yml

but we constantly face this "Cache service responded with 422" as you can see in the image

build with this error: https://github.com/ccxt/ccxt/actions/runs/14494405787/job/40658967886?pr=25731

Action version:
v2

Platform:

• Ubuntu
• macOS
• Windows

Runner type:

• Hosted
• Self-hosted

Tools version:

Python 3.1.11

Repro steps:
Check our public repo: https://github.com/ccxt/ccxt/blob/master/.github/workflows/python.yml

Expected behavior:
Python to be installed

Actual behavior:
422 error

Thanks for your work!

[rpmcginty]

We are also seeing this error in our workflows:

Run actions/setup-python@v2
  with:
    python-version: 3.11
    cache: pip
    token: ***
  env:
    PYTHON_VERSION: 3.11
Successfully setup CPython (3.11.12)
/opt/hostedtoolcache/Python/3.11.12/x64/bin/pip cache dir
/home/runner/.cache/pip
Error: Cache service responded with 422

[jwchae8]

I also faced the same issue while using actions/setup-python@v3.
I could solve it by upgrading setup-python version. It was resolved after using actions/setup-python@v5.
From comments in the similar issue in setup-node, looks like old versions are depending on deprecated package.
setup-node issue
I believe your issue can also be resolved by bumping up.

[priya-kinthali]

Hello👋, thanks for reporting this issue!

The error is occurring because setup-python@v2 relies on a deprecated version of @actions/cache. Upgrading to setup-python@v5 should resolve this issue, as it uses the updated version of the cache service.

To fix this and prevent any further caching problems, please update your workflows to use actions/setup-python@v5.

For more details, you can refer to the discussion here: actions/toolkit#1890.

Feel free to reach out if you need further assistance or clarification!

[rpmcginty]

great thanks for the explanation! upgrading to actions/setup-python@v5 resolved the issue.

[carlosmiei]

@priya-kinthali Thanks for the clarification, will try that out.

[carlosmiei]

Upgrading to v5, fixed it 🥳