Closed jeremyd2019 closed 8 months ago
OK, I see, I got distracted last month and never created a fresh autobuild runner with February's Patch Tuesday updates. It's still running the January one, which still had python installed when the setup-python action was updated from v4 to v5.
Annoying that it makes a node deprecation warning for every job though. I hope they do something about this issue, unlike the actions/toolkit#1311 issue (which the fact that they never did anything about that made me think they don't really care that much about Windows self-hosted runners)
Looks like they might have fixed this in main
branch. Once they update v5
we could probably finally revert this.
https://github.com/actions/setup-python/releases/tag/v5.2.0 - guess I can make a new runner and test it (since mingw-packages uses setup-python@v5) and open a PR here if it works.
I hit https://github.com/actions/setup-python/issues/819 on a fresh self-hosted runner. We might have to revert to v4 until that's fixed (there is a PR but don't know if it is getting any traction, it was 2 weeks ago).