Use Python 3.11.5 for stubtest in CI #10641
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
By using the
check-latest
setting with thesetup-python
action, we ensure that we always get the latest micro version of Python that's available on GitHub Actions, rather than whatever version happens to be lying around in the local cache of today's GitHub Actions runner. This should mean that we get more consistent Python versions in CI when running stubtest -- in the past we've been plagued by issues where some runners started using a new micro version of Python in CI, but other runners were stuck using older micro versions for a week or more.Right now, this has the effect of upgrading the version of Python 3.11 we're using for stubtest to 3.11.5.
Docs on the
check-latest
option: https://github.com/actions/setup-python/blob/main/docs/advanced-usage.md#check-latest-version