Latest stable pypy3.11 release is not available #1360

Activity

1. skirpichev

   added

   bugSomething isn't workingSomething isn't working

   needs triage

   on Sep 24, 2026
2. v-gowridurgad

   removed

   needs triage

   on Sep 24, 2026
3. v-gowridurgad commented on Sep 24, 2026

   

   v-gowridurgad

   on Sep 24, 2026

   Contributor

   More actions

   Hi @skirpichev,
   Thank you for creating this issue. We will investigate it and provide feedback as soon as we have some updates.
4. v-priyagupta108

   self-assigned this

   on Sep 24, 2026
5. eran132 commented on Sep 27, 2026

   

   eran132

   on Sep 27, 2026

   More actions

   This looks like the documented check-latest behaviour rather than a resolution bug. The runner image ships PyPy 3.11 in its tool cache, and that copy predates the 8.0.0 release.

   • ubuntu-24.04 image 20260920.314.1 has 3.11.15 [PyPy 7.3.23] pre-cached (image readme). versions.json was updated with 8.0.0 on Sept 21, a day after that image was built.
   • With the default check-latest: false, setup-python uses any cached version that satisfies pypy3.11 before it looks at the manifest (docs).

   I checked this with actions/setup-python@v7.0.0 and python-version: pypy3.11 (run):

   Runner	check-latest	Result
   ubuntu-24.04	false	PyPy 7.3.23 (Python 3.11.15), from the tool cache
   ubuntu-24.04	true	Resolved as PyPy 8.0.0 with Python (3.11.16), downloaded
   windows-2025	false / true	PyPy 8.0.0. That image has no pypy3.11 cached, so it downloads the newest

   Until the images pick up 8.0.0 in a future rebuild, setting check-latest: true gets the new release:

   - uses: actions/setup-python@v7
     with:
       python-version: pypy3.11
       check-latest: true
6. skirpichev commented on Sep 28, 2026

   

   skirpichev

   on Sep 28, 2026

   Author

   More actions

   Sorry, my fault. Seems to be working in mpmath/mpmath#1194
7. skirpichev

   closed this as not plannedon Sep 28, 2026