Is there an expected timeline for the stable release of 17.0?

[bsmith-self]

We're waiting to upgrade from Node 14 because we don't want to go to an alpha version of graphql for Node 18 support, but trying to decide whether we need to go ahead and upgrade to 16 and then go to 18 a few months from now when 16 is EOL, or just wait and go straight to 18 (if the stable graphql release is right around the corner)

I realize these things can be uncertain, but any information about the time-scale (days? weeks? months?) would be appreciated

[torbjornvatn]

@IvanGoncharov any updates on this!

We really need #2757 Support returning async iterables from resolver functions in some of our production environments, but we have to keep building a separate version with the alpha version because we don't want to use it in all our environments

[philippemiguet]

Same, we really need this patch in production for async iterables. We have our event loop blocked by the execute method when a resolver returns a large array of results and that method needs to generate promises of all field resolvers.

[leszekhanusz]

See also graphql-python/gql#427.

Is there anything blocking a stable release of 17.0?

[jarlefosen]

Hi, is there a roadmap for what's needed in order to release v17? cc @IvanGoncharov