Test Python 3.12 and 3.13 on a push to main that changes the version or the lock #38

Merged

tiagoagueda merged 1 commit from 14-ci-uv into main

2026-11-12 05:06:33 +00:00

tiagoagueda commented

2026-11-11 22:58:57 +00:00

Owner

Closes #14

uv was already pinned (imap#24). A new every-python.yml runs the tests on 3.12 and 3.13 on a push to main that changes pyproject.toml or uv.lock, weekly and by hand, as the core does; pull requests still run 3.14 only. Checked with actionlint; to be seen on its first run.

🤖 Generated with Claude Code

Closes #14 uv was already pinned (imap#24). A new `every-python.yml` runs the tests on 3.12 and 3.13 on a push to `main` that changes `pyproject.toml` or `uv.lock`, weekly and by hand, as the core does; pull requests still run 3.14 only. Checked with actionlint; to be seen on its first run. 🤖 Generated with [Claude Code](https://claude.com/claude-code)

tiagoagueda added 1 commit

2026-11-11 22:58:57 +00:00

Test Python 3.12 and 3.13 on a push to main that changes the version or the lock

CI / test (pull_request) Failing after 2m43s

Details

015d5675e9

requires-python admits 3.12, 3.13 and 3.14, and a plugin is installed into the core's
environment on whichever of them Postulo runs, but the workflows only ever ran 3.14.
The two older Pythons now run in a workflow of their own, as the core's every-python.yml
does: weekly, by hand, and on a push to main that changes pyproject.toml or uv.lock, so
a release's merge runs them on the commit that is tagged. Pull requests and issue
branches still run 3.14 alone, and take as long as before.

The other half of the issue, the unpinned uv installer, was already done by #24: both
workflows install uv 0.12.17 and check the installer's sha256, the same version and
digest as the core's ci.yml on main.

Closes #14

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>