Skip to content

Python support policy: widen to <3.15, CI-test 3.13 + bugfix-tier 3.14 (allow-fail) - #100

Merged
nycomp merged 2 commits into
mainfrom
py-support-policy
Oct 7, 2026
Merged

nycomp merged 2 commits into
mainfrom
py-support-policy

Conversation

@nycomp

@nycomp nycomp commented Oct 7, 2026

Copy link
Copy Markdown
Contributor

Summary

Aligns campus-api-python with the department Python support policy (2026-10-07 tier boundary: 3.13 crossed bugfix→security, 3.14 is now the bugfix tier):

  • pyproject: >=3.11,<3.14 → >=3.11,<3.15 — security tier 3.11–3.13 (officially supported), bugfix tier 3.14 admitted for CI.
  • CI matrix gains 3.13 (previously declared but never tested — a support-promise gap) and a 3.14 leg under continue-on-error (runs for signal, never blocks).
  • Lock refreshed against the widened campus-suite weekly (merged as campus#849); pinned versions preserved.

Note: the lock's transitive campus-api-python entry briefly follows campus's interim dependency pin (its py-support-policy branch) until campus's flip-back PR lands on weekly; it self-heals on the next relock.

Widen the Python range to >=3.11,<3.15 so the lock admits bugfix-tier
3.14 (unofficial 'eventually' support: CI-tested with failures allowed,
never deployed to prod). Security tier 3.11-3.13 stays CI-required; the
matrix gains 3.13 (declared but never tested before) and 3.14 (soft leg
via continue-on-error).
Campus weekly now declares >=3.11.0,<3.15 (bugfix-tier 3.14 admitted),
so this lock can track it. Pinned versions preserved; campus-suite
resolved to the widened weekly tip. Transitive campus-api-python
briefly follows campus's interim pin (its widening branch) until the
flip-back PR lands on weekly.
@nycomp
nycomp merged commit bcfbdaa into main Oct 7, 2026
4 checks passed
@nycomp
nycomp deleted the py-support-policy branch October 7, 2026 05:49
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.

2 participants