Skip to content

Commit 52cf067

Browse files
Technologicatclaude
andcommitted
Run coverage on the newest supported Python
The coverage job had frozen at whatever was newest the day the file was written, which left it several versions behind the CI matrix. A coverage run on an old interpreter never exercises the newest-syntax paths, which is where new code lives — and for this project those paths are the point. Internal only: no behavior change, so no changelog entry. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
1 parent 904eeeb commit 52cf067

1 file changed

Lines changed: 7 additions & 1 deletion

File tree

.github/workflows/coverage.yml

Lines changed: 7 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -19,14 +19,20 @@ jobs:
1919
runs-on: ubuntu-latest
2020
strategy:
2121
matrix:
22-
python-version: ["3.12"]
22+
# The newest Python the project supports, i.e. the top of the CI matrix —
23+
# that is where new-syntax code paths actually run. Bump this whenever the
24+
# matrix grows; nothing else will remind you.
25+
python-version: ["3.15"]
2326

2427
steps:
2528
- uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
2629
- name: Set up Python ${{ matrix.python-version }}
2730
uses: actions/setup-python@5fda3b95a4ea91299a34e894583c3862153e4b97 # v7.0.0
2831
with:
2932
python-version: ${{ matrix.python-version }}
33+
# 3.15 is at rc1, which the setup-python manifest marks unstable, so a bare
34+
# "3.15" resolves to nothing without this. Becomes a no-op once 3.15 final ships.
35+
allow-prereleases: true
3036
- name: Install tools in CI virtualenv
3137
run: |
3238
python -m pip install --upgrade pip

0 commit comments

Comments
 (0)