Below are some comments to respond more broadly about your well brought up concerns (no idea at the moment what would be a good 'instruction').

• We run github tests on python 3.7; 3.8 & 3.9.
• readthedocs needs to be configured to one Python version. 3.8 (to me) appears as the best bridge between these versions—yet, at some point, python 3.11 is beyond release candidate and 3.7-3.10 will become deprecated - after a period for security updates, the whole pytorch ecology will have no chance but to migrate to the new space - end of life: 3.7 (27 Jun 2023); 3.8 (14 Oct 2024); 3.9 (05 Oct 2025)—when 3.8 turns deprecated, why even bother to adopt python 3.10 ? ;-)
• likewise, pre-commit checks need to operate on one specific version—the github checks cover 3.7 to 3.9 versions (if there'd be an issue, it comes clear there—haven't seen that happening thus far though)
• pypi step also needs to use a specific version, I'd assume—3.8 seems a reasonable choice for the time being

You have good points—pretty good catches !