This kind of thing, by the way, is one of the main reasons that I am so bad at getting anything done in OSS anymore. My free time is at an extreme premium, and whenever I steal half an hour to try to merge an uncontroversial PR or something, it gets eaten up fixing bitrot. ☹
@pganssle Hmmm in addition, could also evaluate using actions/setup-python@v4 instead of actions/setup-python@v1as I'm not sure what differences/updates have happened that may be providing better functionality
@scriptautomate @pganssle Yep, ubuntu-20.04, macos-10.15 and windows-2019, and bumping the GitHub Actions is needed.
@pganssle From what I can tell, it looks like Python 3.6 is available out of box on:
- Windows Server 2019
- MacOS 10.15
You can find that Python 3.6.x is available as a cached tool in the runner images for those two, by following the links from here:
https://docs.github.com/en/actions/using-github-hosted-runners/about-github-hosted-runners#preinstalled-software
Your failing jobs use Windows Server 2022 and MacOS 12, which don't have Python 3.6.x available in the cached tools.
An alternative could be to maybe use something like pyenv if wanting to support the newer OS runners?