Add CI testing against Python beta versions #18

Closed
opened 2026-06-13 06:45:55 +00:00 by coding-agent-marvin8 · 1 comment
coding-agent-marvin8 commented 2026-06-13 06:45:55 +00:00 (Migrated from codeberg.org)

The noxfile already defines BETA_PYTHONS = ["3.15", "3.15t"] and a pytest_betas session, but there is no CI step that invokes it. Add a dedicated pytest_betas step to .woodpecker/checks.yml (with failure: ignore) so beta failures surface without blocking the pipeline.

The noxfile already defines BETA_PYTHONS = ["3.15", "3.15t"] and a pytest_betas session, but there is no CI step that invokes it. Add a dedicated pytest_betas step to .woodpecker/checks.yml (with failure: ignore) so beta failures surface without blocking the pipeline.
coding-agent-marvin8 commented 2026-06-13 06:46:04 +00:00 (Migrated from codeberg.org)

noxfile.py already has the pytest_betas session targeting Python 3.15 and 3.15t (following the same pattern as zaojun). The only change needed is in .woodpecker/checks.yml: add a pytest_betas step after the checks step, using failure: ignore so beta failures are visible but don't block the pipeline. Files to change: .woodpecker/checks.yml (new step), noxfile.py (include in commit per TODO requirement), TODO.md (mark #6 done).

noxfile.py already has the pytest_betas session targeting Python 3.15 and 3.15t (following the same pattern as zaojun). The only change needed is in .woodpecker/checks.yml: add a pytest_betas step after the checks step, using failure: ignore so beta failures are visible but don't block the pipeline. Files to change: .woodpecker/checks.yml (new step), noxfile.py (include in commit per TODO requirement), TODO.md (mark #6 done).
Sign in to join this conversation.
No labels
No milestone
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Reference
marvin8/taibai#18
No description provided.