Stable 3.5.x release?

[aalmazan]

Hello, I was wondering if there are any near-term plans on getting a stable version of version 3.5 out? There were some recent changes that made it into v3.5.0b1 (and thank you again for the quick issue update btw), but we have a few new constraints that require a stable version to be used.

I realize it's just a label, but it would be helpful to get it released into a stable release. Any thoughts appreciated. If there are any tasks along the way that I can help with, I wouldn't mind taking a look if it falls within my expertise.

[leszekhanusz]

The problem is that the current pre-release version of gql is based on the alpha version of graphql-core 3.3.0a3, which itself is based on the alpha version of graphql-js 17.0.0-alpha.2.

And we have no idea when graphql-js will make a stable release of 17.0

[dacevedo12]

Would it be possible to release a 3.4.x with the HTTPX transport? would find it useful

[divad]

+1, since we cannot use the requests transport, can a 3.4.x release be added with httpx support please?

[cdce8p]

Aiohttp 3.9.0 is expected to be released this weekend. I would also appreciate a new 3.4.x release, with #425 backported.

[werkshy]

aiohttp < 3.9.0 now has a high severity CVE - the gql pin on < 3.9.0 is preventing many folks from addressing this. A 3.4.x release would be much appreciated.

[leszekhanusz]

Alright, to solve this conundrum I modified the tests to allow to easily switch between graphql-core versions, then I reverted graphql-core to its stable version in a new stable branch and made the new stable gql version 3.5.0

A new pre-release version 3.6.0b0 has also been made for those who need graphql-core alpha versions.

[drcrazy]

PURE AWESOMENESS!!! We can now bump aiohttp. Thank you a lot!