I don't believe v3.9.0b0 should be on the main label

[xylar]

Solution to issue cannot be found in the documentation.

• I checked the documentation.

Issue

pip check is failing for downstream packages that have aiohttp <3.9.0 because they pick up 3.9.0b0. I had to constrain a package to have aiohttp < 3.8.6 to avoid this:
conda-forge/alibabacloud-tea-feedstock#1

Not a giant problem but a minor inconvenience.

I guess this version was added to the main label in #76 to allow python 3.12 support? Maybe it's time to move it to a dev-aiohttp label?

Installed packages

N/A

Environment info

N/A