Skip to content

ci: pin python-version on compile job's setup-python step#187

Merged
gavinsharp merged 1 commit into
mainfrom
gavinsharp/set-python-version
Jun 15, 2026
Merged

ci: pin python-version on compile job's setup-python step#187
gavinsharp merged 1 commit into
mainfrom
gavinsharp/set-python-version

Conversation

@gavinsharp

@gavinsharp gavinsharp commented Jun 15, 2026

Copy link
Copy Markdown
Contributor

Summary

The compile job's setup-python step had no explicit python-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 the compile job's setup-python step, matching the test and publish jobs and the project's minimum supported version (python = "^3.10"). CI-only change; no API, package, or user-facing impact.

Testing

  • Verified the test and publish jobs already pin the same value, so compile is 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 compile job’s setup-python step now sets python-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 compile with the test and publish jobs and with the package floor in pyproject.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.

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>
@gavinsharp gavinsharp merged commit 52e6ed6 into main Jun 15, 2026
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants