Those versions are done insomuch as they won’t get any more releases as they are in security-only mode and thus don’t get binary releases.
I also changed how I do builds at GitHub - brettcannon/cpython-wasi-build: Unofficial WASI builds of CPython so that there is a branch per Python version once they are branched off of CPython’s main branch (i.e. main on my repo is for 3.14 until main at the CPython repo becomes 3.15 next month). The new approach makes it a bit easier for me since I have less things to specify when doing a new release.
I’m pinning the WASI SDK version to make my life simple. The versions are:
- 3.11: 16
- 3.12: 20
- 3.13: 24
- 3.14: 24
3.15 will be determined when a1 is released. The expectation is this will eventually become the official policy for CPython support of WASI once I get enough time to write a PEP for such a policy. 
(And if any of this interests you then you should attend the Bytecode Alliance Python subgroup meetings and/or comment on the BA’s Zulip instance).