Skip to content

Conversation

@mishushakov
Copy link
Member

@mishushakov mishushakov commented Feb 9, 2026

Summary

  • Upgrade all Python workflow jobs from Python 3.12 (and 3.10 for linting) to Python 3.13
  • Update setup-python action from v4 to v6 to support Python 3.13

Affected Workflows

  • charts_tests.yml
  • lint.yml
  • performance_tests.yml
  • python_tests.yml
  • release.yml (multiple jobs)
  • release_candidates.yml

🤖 Generated with Claude Code


Note

Low Risk
CI-only change that bumps the Python runtime and actions/setup-python version; main risk is workflow breakage if dependencies/tools don’t yet support Python 3.13.

Overview
Updates GitHub Actions workflows to run Python jobs on Python 3.13 (including linting, tests, performance tests, and release/release-candidate pipelines), replacing prior 3.10/3.12 usage.

Upgrades actions/setup-python from v4 to v6 across these workflows to support the new Python version.

Written by Cursor Bugbot for commit 03b8306. This will update automatically on new commits. Configure here.

Upgrade all Python workflow jobs from Python 3.12 (and 3.10 for linting) to Python 3.13, and update setup-python action from v4 to v6 to support the new version.

Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>
Copy link

@cursor cursor bot left a comment

Choose a reason for hiding this comment

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

Cursor Bugbot has reviewed your changes and found 2 potential issues.

Bugbot Autofix is OFF. To automatically fix reported issues with Cloud Agents, enable Autofix in the Cursor dashboard.

uses: actions/setup-python@v6
with:
python-version: '3.12'
python-version: '3.13'
Copy link

Choose a reason for hiding this comment

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

NumPy 1.26.4 incompatible with Python 3.13 in charts

High Severity

The chart_data_extractor project depends on numpy = "^1.26.4" (constrained to <2.0.0), but NumPy 1.26.4 has Requires-Python: <3.13,>=3.9 and is the last 1.x release. Upgrading Python to 3.13 makes it impossible to install numpy within that version constraint, so poetry install will fail. The pyproject.toml constraint needs to be updated to allow NumPy 2.x before switching to Python 3.13.

Additional Locations (1)

Fix in Cursor Fix in Web

Copy link
Member Author

Choose a reason for hiding this comment

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

we will upgrade it

uses: actions/setup-python@v6
with:
python-version: '3.12'
python-version: '3.13'
Copy link

Choose a reason for hiding this comment

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

NumPy 2.0.2 lacks Python 3.13 support in SDK

High Severity

The python/poetry.lock pins numpy to 2.0.2, which has no cp313 wheels. NumPy 2.1.0 was the first version to add Python 3.13 support (per its release notes). On Python 3.13, Poetry would fall back to building numpy 2.0.2 from source, which is expected to fail because the C code was not updated for Python 3.13 API changes. This breaks python_tests.yml, performance_tests.yml, and lint.yml at poetry install.

Additional Locations (2)

Fix in Cursor Fix in Web

Copy link
Member Author

Choose a reason for hiding this comment

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

it's fine, we can update it at later point

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.

1 participant