fix: tourney stream handling in get_allowed_client_versions

[TrueRou]

Describe your changes

tourney client can't connect to bancho due to old clients, as https://osu.ppy.sh/api/v2/changelog?stream=tourney has an empty builds list.

in fact, tourney client use the same channel as the its base osu stream(stable).

Related Issues / Projects

Checklist

• I've manually tested my code

[7ez]

I'm pretty sure you can use tourney on cutting-edge too, no?

[TrueRou]

I'm pretty sure you can use tourney on cutting-edge too, no?

After testing, sure it can.

The sent "v" was like b20250702tourney, so we might have to join stable and cutting-edge builds on tourney channels checking, as we can't distinguish between them by "v"

[arily]

I have another related question,

    if osu_version.stream is OsuStream.TOURNEY and not (
        user_info["priv"] & Privileges.DONATOR
        and user_info["priv"] & Privileges.UNRESTRICTED
    ):
        # trying to use tourney client with insufficient privileges.
        return {
            "osu_token": "no",
            "response_body": app.packets.login_reply(
                LoginFailureReason.AUTHENTICATION_FAILED,
            ),
        }

(

bancho.py/app/api/domains/cho.py

Line 725 in 7429091

if osu_version.stream is OsuStream.TOURNEY and not (

)
shouldn't TOURNEY_MANAGER be given access to tourney client as well?

[arily]

I have another related question,

    if osu_version.stream is OsuStream.TOURNEY and not (
        user_info["priv"] & Privileges.DONATOR
        and user_info["priv"] & Privileges.UNRESTRICTED
    ):
        # trying to use tourney client with insufficient privileges.
        return {
            "osu_token": "no",
            "response_body": app.packets.login_reply(
                LoginFailureReason.AUTHENTICATION_FAILED,
            ),
        }

(

bancho.py/app/api/domains/cho.py

Line 725 in 7429091

if osu_version.stream is OsuStream.TOURNEY and not (

)
shouldn't TOURNEY_MANAGER be given access to tourney client as well?

ppy-sb#10

[mayacopeland]

nevermind

[NiceAesth]

i very much disagree with doing a request in a for loop here, why are we not just requesting OSU_API_V2_CHANGELOG_URL, iterating over the streams and getting dates from the latest_build?

[NiceAesth]

also, looking at the current response i can't seem to see anything about major versions anymore

[NiceAesth]

as above