Repository navigation
ci: run the floor, coverage and newest Python legs on pull requests - #63
Merged
Merged
Conversation
A pull request now runs Python 3.10, 3.12 and 3.14. The push to main still runs all five supported versions, so main keeps the full verdict. The artifact contract test now asserts that split instead of one list.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changes
Testsruns the 3.10 floor, the 3.12 coverage leg and 3.14 onpull_request. The push tomainstill runs 3.10 through 3.14.Required CI, itsneedslist and every other job are unchanged.tests/test_ci_artifact_contract.pynow asserts the split: the push set equals the supported versions, and the PR set holds the floor, the coverage version and the newest version.Measured (2026-10-11 to 2026-10-25, job durations rounded up per job)
Tests: 11 runs at about 13 billed minutes each (lint 1, gate 1, 3.12 with coverage 3, the other four legs 2 each). 6 runs werepull_requestand 5 werepush.Testsruns since 2026-06 failed on 3.11 or 3.13 alone. Each one was a lint failure or failed on every leg.Projected
Not changed, and why
mainstays. The repository has no ruleset that requires branches to be up to date, so the squash commit can differ from the tree the PR run tested.Monthly Pipeline Refreshstays as it is. It is public and used about 43 minutes on 2026-10-01.Context: what actually exhausted the MAPS-Lab budget
The MAPS-Lab Actions budget is $50 with
prevent_further_usage: true. October hit $50.03 net on 2026-10-11. Most of that came from the privateMAPS-Lab/OceanStackdaily scheduled full matrix, at about $4.89 a run. CiteForge is not a cause. It does feed the privatemapslab-websitedeploy, though, and that deploy is blocked until the budget clears. That fix is in a separate OceanStack PR.Verification
.venv/bin/pytest -m 'not live' -qon rtx, Python 3.12, against 4a6f886 plus this diff: 2083 passed, 2 skipped (the two cutover contracts that are skipped by design), 7 deselected (live).ruff check citeforge/ tests/ main.pyis clean.actionlintandzizmor --offlinereport nothing ontests.yml.