4.9.3 cp311 manylinux aarch64 wheel was bumped incorrectly to manylinux_2_28

Something seems to have been changed or gone wrong while building and/or uploading the cp311 manylinux wheels of release 4.9.3:
https://pypi.org/project/lxml/4.9.2/#files
https://pypi.org/project/lxml/4.9.3/#files

4.9.2:
- lxml-4.9.2-cp311-cp311-manylinux_2_17_x86_64.manylinux2014_x86_64.manylinux_2_24_x86_64.whl
- lxml-4.9.2-cp311-cp311-manylinux_2_17_aarch64.manylinux2014_aarch64.manylinux_2_24_aarch64.whl
- lxml-4.9.2-cp311-cp311-manylinux_2_12_i686.manylinux2010_i686.manylinux_2_24_i686.whl

4.9.3:
- lxml-4.9.3-cp311-cp311-manylinux_2_28_x86_64.whl
- lxml-4.9.3-cp311-cp311-manylinux_2_28_aarch64.whl
- lxml-4.9.3-cp311-cp311-manylinux_2_17_x86_64.manylinux2014_x86_64.manylinux_2_24_x86_64.whl
- lxml-4.9.3-cp311-cp311-manylinux_2_12_i686.manylinux2010_i686.manylinux_2_24_i686.whl

As you can see, this unintentionally bumps the glibc requirement on aarch64 from 2.17 to 2.28. However, wheels for x86_64 and i686 were still built and uploaded with support for glibc 2.17. If this was changed intentionally, then this is a breaking change which instead should be included in 5.0.0 and not in 4.x.

This means that I can't install the latest lxml wheel in my CentOS7-based docker image (pypa manylinux2014) where I currently still build the Linux AppImages for my application (support ends next year), and it unfortunately breaks my build script.

Please have a look at the 4.9.3 cp311 manylinux wheels. Thanks!