Skip to content

Upgrade repo to Python 3.14#759

Merged
adilhafeez merged 1 commit intomainfrom
adil/python_3_14
Feb 15, 2026
Merged

Upgrade repo to Python 3.14#759
adilhafeez merged 1 commit intomainfrom
adil/python_3_14

Conversation

@adilhafeez
Copy link
Copy Markdown
Contributor

@adilhafeez adilhafeez commented Feb 15, 2026

Summary

  • Upgrade all GitHub Actions python-version from 3.12 to 3.14 (8 jobs in ci.yml, 1 in publish-pypi.yml); e2e matrix kept as-is (already includes 3.14)
  • Upgrade all Dockerfiles to python:3.14 / python:3.14-slim base images (main Dockerfile + 7 demo Dockerfiles)
  • Remove upper bound (<3.13.3) on requires-python in model_choice_with_test_harness/pyproject.toml and regenerate its uv.lock
  • Update e2e README prerequisite from "Python 3.10" to "Python 3.10+"

Update all GitHub Actions workflows and Dockerfiles to use Python 3.14
as the default version. Remove the upper bound on requires-python in
model_choice_with_test_harness to allow 3.14+. The CLI's
requires-python stays at >=3.10 for broad compatibility.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Copy link
Copy Markdown
Contributor

@salmanap salmanap left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you please confirm if this requires developers to have Python 3.14? I believe this is for our internal builds and for demos. Correct? If so, please go ahead and merge. But we shouldn't impose 3.14 to uv tool install planoai

@adilhafeez
Copy link
Copy Markdown
Contributor Author

3.14 requirement is only for github actions and for our internal runs. For developers we still support python 3.10+

@adilhafeez adilhafeez merged commit c3591bc into main Feb 15, 2026
20 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