CI workflow improvements - #603

Can you rebase on top of main? Also I'd keep at least the scheduled workflows, they're the ones that give us a better chance of exposing things that don't trigger on every run like resource mismanagement (#575).

@mistotebe I rebased the branch, restored the scheduled run and added support for Python 3.15 (recently released) (mypy on py3.15 makes a leftover problem).

Yeah, I reproduced the mypy failure: uv: "0.9" selects Python 3.15.0a5, whose ABI cannot load the librt wheel. With uv 0.13.4 selecting released 3.15.0, all runtime tests and the constants/mypy/stubtest checks pass unchanged; filelock 4.2.3 fixes only the separate shutdown traceback.

I'd update uv and retain the old job names, since all 14 required checks still use them, while keeping the restored schedule and existing typing checks.

Yeah, I reproduced the mypy failure: uv: "0.9" selects Python 3.15.0a5, whose ABI cannot load the librt wheel. With uv 0.13.4 selecting released 3.15.0, all runtime tests and the constants/mypy/stubtest checks pass unchanged

Ahh, thanks :-)

retain the old job names, since all 14 required checks still use them

Where are these names configured? I see that some of the pipelines here which were renamed forever end with "Waiting status to be reported". I had this in the past in other MRs as well.

All passing now :-)

I would like to close this in favor of #686

Fine with me.