actions
MS-Windows 2022 image 20250609 has a bug with Python 3.13.4
Description
We are seeing a build error in https://github.com/vim/vim when building Vim with dynamic python.
Logfile: https://github.com/vim/vim/actions/runs/15570836046/job/43851117962#step:9:233 Vim bug Python bug:
Platforms affected
- [ ] Azure DevOps
- [x] GitHub Actions - Standard Runners
- [ ] GitHub Actions - Larger Runners
Runner images affected
- [ ] Ubuntu 22.04
- [ ] Ubuntu 24.04
- [ ] macOS 13
- [ ] macOS 13 Arm64
- [ ] macOS 14
- [ ] macOS 14 Arm64
- [ ] macOS 15
- [ ] macOS 15 Arm64
- [ ] Windows Server 2019
- [x] Windows Server 2022
- [ ] Windows Server 2025
Image version and build link
Example failing build Logfile
Is it regression?
yes, didn't happen with image release 20250602
Expected behavior
See the python version difference between 20250602 and 20250609: https://github.com/actions/runner-images/releases/tag/win22%2F20250609.2 https://github.com/actions/runner-images/releases/tag/win22%2F20250602.1
Actual behavior
Build fails
Repro steps
Build Vim with dynamic python and the stable/limited API (see the Vim bug)
@chrisbra Thank you for bringing this issue to our attention. We will look into this issue and will update you after investigating.
Python has released 3.13.5 to fix the significant issue with Windows installs: https://www.python.org/downloads/release/python-3135/. Would be great if a new runner images for Windows could be released soon that have this new Python version instead of the 3.13.4 one.
https://github.com/python/cpython/issues/135151 is effecting python3.13 wheel builds on both windows-2022 and windows-2025 for https://github.com/WojciechMula/pyahocorasick
Hi @chrisbra - The latest image version is scheduled to begin rolling out in coming week. We’ll notify you once it’s available then you can try to update your sync process and verify with the new version and confirm us. Thanks!
Hi @chrisbra - The latest image version has been rolled out. Please update your sync process and try using the new version and confirm us. Thanks!
Hi @chrisbra - Since we haven't heard back, we'll assume your issue is resolved and will close this issue for now. Feel free to reach out to us for any other queries. Thanks.