Drop Python 3.10 support, add 3.14 to CI, bump pipelex to 0.39.0#77
Drop Python 3.10 support, add 3.14 to CI, bump pipelex to 0.39.0#77lchoquel wants to merge 1 commit into
Conversation
Upstream pipelex removed its own 3.10 support and deleted the StrEnum re-export we relied on, so we now import StrEnum from stdlib enum and raise our own minimum to 3.11. Also test against 3.14 in CI and point mypy at local paths instead of module names so an editable pipelex checkout doesn't drag that repo's tests into our type check. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Cg7xzRtbshzke25awsYEud
Greptile SummaryThis PR updates the project for Python 3.11 through 3.14. The main changes are:
Confidence Score: 5/5This looks mergeable after confirming Python 3.14 provisioning in CI. The package metadata, lock file, imports, and documentation consistently require Python 3.11 or later. The updated dependency graph includes a separate Python 3.14 resolution path. The remaining concern is limited to whether the existing setup-python action can provision the new CI interpreter.
What T-Rex did
Important Files Changed
Prompt To Fix All With AIFix the following 1 code review issue. Work through them one at a time, proposing concise fixes.
---
### Issue 1 of 1
.github/workflows/lint-check.yml:20
**Python 3.14 Runner Provisioning**
The new 3.14 matrix leg still uses `actions/setup-python@v4`. If that action version cannot provision Python 3.14 on the hosted runner, every lint run fails during setup and the `lint-all` job blocks the pull request before any lint command runs. Use an action release that supports the newly added interpreter.
Reviews (1): Last reviewed commit: "Drop Python 3.10 support, add 3.14 to CI..." | Re-trigger Greptile |
| fail-fast: false | ||
| matrix: | ||
| python-version: ["3.10", "3.11", "3.12", "3.13"] | ||
| python-version: ["3.11", "3.12", "3.13", "3.14"] |
There was a problem hiding this comment.
Python 3.14 Runner Provisioning
The new 3.14 matrix leg still uses actions/setup-python@v4. If that action version cannot provision Python 3.14 on the hosted runner, every lint run fails during setup and the lint-all job blocks the pull request before any lint command runs. Use an action release that supports the newly added interpreter.
Prompt To Fix With AI
This is a comment left during a code review.
Path: .github/workflows/lint-check.yml
Line: 20
Comment:
**Python 3.14 Runner Provisioning**
The new 3.14 matrix leg still uses `actions/setup-python@v4`. If that action version cannot provision Python 3.14 on the hosted runner, every lint run fails during setup and the `lint-all` job blocks the pull request before any lint command runs. Use an action release that supports the newly added interpreter.
How can I resolve this? If you propose a fix, please make it concise.Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!
Summary
pipelexto 0.39.0; importStrEnumfrom stdlibenuminstead of the now-removedpipelex.typesre-exportfiles) instead of module names (packages) so an editablepipelexcheckout doesn't drag that repo's test suite into our type checkTest plan
make agent-checkandmake agent-testpass locally🤖 Generated with Claude Code
https://claude.ai/code/session_01Cg7xzRtbshzke25awsYEud
Summary by cubic
Drops Python 3.10 support (minimum is now 3.11) and adds 3.14 to the lint/test CI. Upgrades
pipelexto 0.39.0 and updates typing to useenum.StrEnum; mypy now targets local paths only.Dependencies
pipelex→ 0.39.0; devpyright→ 1.1.411.Migration
Written for commit acf0b31. Summary will update on new commits.