PyPy3.10 is v7.3.17 not the latest v7.3.18

[skirpichev]

Description:
New version was released, v7.3.18: https://pypy.org/posts/2025/02/pypy-v7318-release.html

Also beta-version of the PyPy3.11 interpreter is available.

Action version:
latest (v5.4.0)

Platform:

• Ubuntu
• macOS
• Windows

Runner type:

• Hosted
• Self-hosted

[edgarrmondragon]

PyPy3.11 v7.3.18 is available. I have not confirmed yet, but I suppose PyPy3.10 v7.3.18 is also available, since it's present in https://downloads.python.org/pypy/versions.json.

[skirpichev]

On https://pypy.org/download.html both latest PyPy3.11 and PyPy3.10 are available. Both are present in versions.json.

[Mulugruntz]

If I may add, some of our Actions have used 3.13.1 and some have used 3.13.2 (python-version: 3.13).
It seems non-deterministic.
I cleared the cache, and it was the same, some PRs are picking up 3.13.1 instead of 3.13.2.

[skirpichev]

FYI: I did several restarts on diofant/python-gmp#127 - it always uses v7.3.17 (for pypy3.10).

[edgarrmondragon]

FYI: I did several restarts on diofant/python-gmp#127 - it always uses v7.3.17 (for pypy3.10).

The Python executable is cached AFAICT, but it's definitely available

Installed versions
  Successfully set up PyPy 7.3.18 with Python (3.10.16)
/opt/hostedtoolcache/PyPy/3.10.16/x64/bin/pip cache dir
/home/runner/.cache/pip
Cache hit for: setup-python-Linux-x64-24.04-Ubuntu-python-7.3.18-3.10.16-pip-30b33c76dc2eaf033f8e4f81c126eb8f128caf52326db89b83820e8d097b7a43
Received 25165824 of 40316900 (62.4%), 24.0 MBs/sec
Received 40316900 of 40316900 (100.0%), 33.9 MBs/sec
Cache Size: ~38 MB (40316900 B)
/usr/bin/tar -xf /home/runner/work/_temp/393e5194-b1e6-4b27-8f99-3c9e66a66c65/cache.tzst -P -C /home/runner/work/pep610/pep610 --use-compress-program unzstd
Cache restored successfully
Cache restored from key: setup-python-Linux-x64-24.04-Ubuntu-python-7.3.18-3.10.16-pip-30b33c76dc2eaf033f8e4f81c126eb8f128caf52326db89b83820e8d097b7a43

(from https://github.com/edgarrmondragon/pep610/actions/runs/13291446273/job/37113015486#step:3:14)

[skirpichev]

The Python executable is cached AFAICT

caching is turned off by default (which is my case, for example)

BTW, with latest re-run I got 7.3.18: https://github.com/diofant/python-gmp/actions/runs/13279716587/job/37129536312

[skirpichev]

I see, check-latest is by default still false.

[aparnajyothi-y]

Hi @skirpichev , @Mulugruntz,

Thank you for creating this issue. We’ve investigated the problem with PyPy 3.10 and PyPy 3.11 and observed that it is picking version v7.3.18, and for PyPy 3.13, I am seeing the installation of version 3.13.2. Please find the screenshots for reference.
This issue might be related to the fact that the latest available versions for PyPy are 3.9.19 (PyPy 7.3.16), 3.10.14 (PyPy 7.3.17), and 3.13.1 for python 3.13 on the ubuntu-24.04 image, as per this documentation. To ensure you always get the latest patch version, you can include the check-latest: true input in your workflow configuration, as check-latest is set to false by default. You can find more details on check-latest here.
If these versions need to be updated, please raise an issue in the runner images repository.

[lysnikolaou]

Not sure why I got pinged here. Is there something I could do to help?

[aparnajyothi-y]

Hello @lysnikolaou, Apologies, your name was tagged by mistake. Please disregard the above comment. Thank you!