ci: pin python-version on compile job's setup-python step#187
Merged
Conversation
The compile job was the only setup-python step without an explicit python-version, producing a warning that the version of Python in PATH would be used. Pin it to "3.10" to match the test and publish jobs and the project's minimum supported version (python = "^3.10"). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
kerbearasaurus
approved these changes
Jun 15, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
The
compilejob'ssetup-pythonstep had no explicitpython-version, which emitted a warning that "the version of Python currently in PATH will be used." This pins it so the version is deterministic.Changes & impact
Pins
python-version: "3.10"on thecompilejob'ssetup-pythonstep, matching thetestandpublishjobs and the project's minimum supported version (python = "^3.10"). CI-only change; no API, package, or user-facing impact.Testing
testandpublishjobs already pin the same value, socompileis now consistent.🤖 Generated with Claude Code
Note
Low Risk
Workflow-only change that selects a Python version for CI; no application code or release behavior changes.
Overview
The
compilejob’ssetup-pythonstep now setspython-version: "3.10", so mypy runs on a fixed interpreter instead of whatever Python is already on the runner PATH (which triggered a setup-python warning).This aligns
compilewith thetestandpublishjobs and with the package floor inpyproject.toml(^3.10). CI-only; no runtime or API changes.Reviewed by Cursor Bugbot for commit e36dbbc. Bugbot is set up for automated code reviews on this repo. Configure here.