Added Test support for Python 3.15 - #6897
Conversation
Greptile SummaryThe PR expands CI coverage to Python 3.15 and moves both performance workflows from Python 3.14 to Python 3.15.
Confidence Score: 5/5The PR appears safe to merge. No blocking failure remains.
|
| Filename | Overview |
|---|---|
| .github/workflows/integration_app_harness.yml | Adds Python 3.15 to both app-harness test matrices using the existing uv-based environment setup. |
| .github/workflows/integration_tests.yml | Adds Python 3.15 coverage to the cross-platform integration-test matrix. |
| .github/workflows/performance.yml | Moves benchmark and Lighthouse jobs to Python 3.15 and explicitly enables prereleases for the direct setup-python path. |
| .github/workflows/unit_tests.yml | Adds Python 3.15 to the Linux and Windows unit-test matrix. |
Reviews (3): Last reviewed commit: "Added Test support for Python 3.15" | Re-trigger Greptile
There was a problem hiding this comment.
1 issue found across 4 files
Prompt for AI agents (unresolved issues)
Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.
<file name=".github/workflows/unit_tests.yml">
<violation number="1" location=".github/workflows/unit_tests.yml:31">
P2: The `unit-tests` matrix adds "3.15", but the sibling `unit-tests-macos` matrix in the same file still only lists 3.10–3.14. Since this PR is titled "Added Test support for Python 3.15" and every other workflow already runs 3.15 on linux/windows, Python 3.15 is left untested on macos (the macos job runs on every main push). Add "3.15" to the macos matrix as well, or confirm the omission is intentional.</violation>
</file>
Reply with feedback, questions, or to request a fix.
Re-trigger cubic
| matrix: | ||
| os: [ubuntu-latest, windows-latest] | ||
| python-version: ["3.10", "3.11", "3.12", "3.13", "3.14"] | ||
| python-version: ["3.10", "3.11", "3.12", "3.13", "3.14", "3.15"] |
There was a problem hiding this comment.
P2: The unit-tests matrix adds "3.15", but the sibling unit-tests-macos matrix in the same file still only lists 3.10–3.14. Since this PR is titled "Added Test support for Python 3.15" and every other workflow already runs 3.15 on linux/windows, Python 3.15 is left untested on macos (the macos job runs on every main push). Add "3.15" to the macos matrix as well, or confirm the omission is intentional.
Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. At .github/workflows/unit_tests.yml, line 31:
<comment>The `unit-tests` matrix adds "3.15", but the sibling `unit-tests-macos` matrix in the same file still only lists 3.10–3.14. Since this PR is titled "Added Test support for Python 3.15" and every other workflow already runs 3.15 on linux/windows, Python 3.15 is left untested on macos (the macos job runs on every main push). Add "3.15" to the macos matrix as well, or confirm the omission is intentional.</comment>
<file context>
@@ -28,7 +28,7 @@ jobs:
matrix:
os: [ubuntu-latest, windows-latest]
- python-version: ["3.10", "3.11", "3.12", "3.13", "3.14"]
+ python-version: ["3.10", "3.11", "3.12", "3.13", "3.14", "3.15"]
runs-on: ${{ matrix.os }}
</file context>
All Submissions:
Type of change
Please delete options that are not relevant.
The Python 3.15 beta is out. so from source:
This includes creating pre-release wheels for 3.15, as it helps other projects to do their own testing. However, we recommend that your regular production releases wait until 3.15.0rc1, to avoid the risk of ABI breaks.
I took reference from #5859
does this make sense ?