-
Notifications
You must be signed in to change notification settings - Fork 70
release: v3.0.0b7 #122
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
release: v3.0.0b7 #122
Conversation
@kiendang Any reason not to go straight to RC1 this time? Afaik we're up to date on the frameworks now, and we can always deliver async/WS support in later releases.
No particular reason. Yup I think we're good for RC1.
8a5fb8e to
7b2069f
Compare
Ah actually aiohttp just released their first 3.9 beta version (3.9.0b0) to support python 3.12. See aio-libs/aiohttp#7675.
Plus looks like there's a failed test in test_version.py (https://github.com/graphql-python/graphql-server/actions/runs/6525071080/job/17717371331?pr=122) when I tried to change version to 3.0.0rc1. How about we do a 3.0.0b7 now then do RC1 later when aiohttp 3.9.0 stable is out plus adding tests for Python 3.12? I'll fix the tests too.
@kiendang sounds good! Test is probably breaking because we haven't done any RCs here yet. If we push the beta I'm all open for going straight to major release after that. No major graphql-server functionality should change anymore by waiting for 3.12.
7b2069f to
314451a
Compare
No description provided.