A push to a pull request or to a branch started new runs of the Build and Build binaries workflows while the runs for the older commit went on to the end, holding the runners for results nobody needs.
The Build workflow now has a concurrency group per pull request, and the build jobs of Build binaries one per branch or pull request, with cancel-in-progress: the run for the older commit is cancelled when a newer one starts. Pushes to master get a group of their own (the commit), so the runs on master are neither cancelled nor held back by one another. In Build binaries the groups are on the build jobs, not on the workflow, so a publish job already running is left to finish.
sonar.yml needs no change: it already posts an error status (analysis skipped) on the commit of a cancelled Build run, and the newer commit gets its own pending status and analysis.
- The Windows build job installs Pillow into the Python 3.14 whose Lib, with
site-packages, CMake copies next to the executable as python64\Lib, as the
Linux job already does; the README says the same for a local build.
- Both build jobs copy staticFiles/python/local (the Python 3 version of the
module every cab screen subclasses) into python/local of the build.
- The module puts back what Pillow 10 removed and the screen scripts use:
ImageFont.getsize() and ImageDraw.textsize() on top of getbbox() /
textbbox(), and Image.ANTIALIAS as LANCZOS. With an older Pillow nothing
changes.
Part of #300.