You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are no releases on this repo for b8, b9, or 3.0.0. There are no tags either. I cannot find a changelog, or good place to review changes.
As a heads up, for someone consuming a library, this starts to look like a supply chain attack when there are 3 pypi releases in one day, with no supporting docs, reference, changelog etc.
Reacted by Juan, Akseli Aarnio, Sha, voj, Burton DeWilde, Higa-kun, Cameron, Stefano Tabacco, iamthad and Nic Wolff
There are no releases on this repo for b8, b9, or 3.0.0. There are no tags either. I cannot find a changelog, or good place to review changes.
As a heads up, for someone consuming a library, this starts to look like a supply chain attack when there are 3 pypi releases in one day, with no supporting docs, reference, changelog etc.
Hi, I don't use graphql-python anymore and the one in charge is @syrusakbary, which seems inactive once again. However, it seems like they forgot to document the v3.0.0 release in the repo.
Activity
syrusakbary commentedon Aug 18, 2025
Hey @cameronclaero , the API for using GraphQL-server 3.0 has changed since 3.0.0b7. Please see the examples on how to use it
kaime commentedon Aug 19, 2025
The issue I had was with aiohttp. I had to switch from:
To:
If it's intentional, then I guess the docs need to be updated: https://github.com/graphql-python/graphql-server/blob/main/docs/aiohttp.md#usage
ElementalWarrior commentedon Aug 26, 2025
There are no releases on this repo for b8, b9, or 3.0.0. There are no tags either. I cannot find a changelog, or good place to review changes.
As a heads up, for someone consuming a library, this starts to look like a supply chain attack when there are 3 pypi releases in one day, with no supporting docs, reference, changelog etc.
KingDarBoja commentedon Mar 25, 2026
Hi, I don't use graphql-python anymore and the one in charge is @syrusakbary, which seems inactive once again. However, it seems like they forgot to document the v3.0.0 release in the repo.