graphene-mongo
graphene-mongo copied to clipboard
Bump graphene from 3.0b7 to 3.0
@arunsureshkumar : do you have time to take a look? thanks.
Just a quick note, there are still other graphql-python related code items without these dependencies upgraded that can cause issues with dependency resolution (ie graphene-sqlalchemy)
Also one more item, the graphene version for dev purposes is actually 3.0.0b7 NOT 3.0b7 @abawchen
https://github.com/graphql-python/graphene/releases/tag/v3.0.0b7
@abawchen @arunsureshkumar any chance we can merge this soon?
@abawchen @arunsureshkumar Any chance we can resolve this?
Will work on this at the earliest!
On Tue, 1 Feb 2022 at 8:28 PM, blochs @.***> wrote:
@abawchen https://github.com/abawchen @arunsureshkumar https://github.com/arunsureshkumar Any chance we can resolve this?
— Reply to this email directly, view it on GitHub https://github.com/graphql-python/graphene-mongo/pull/186#issuecomment-1026932613, or unsubscribe https://github.com/notifications/unsubscribe-auth/AEIAZMEY2PUPSWQIYNVV243UY7YINANCNFSM5MFUKKGA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you were mentioned.Message ID: @.***>
duplicate of https://github.com/graphql-python/graphene-mongo/pull/191
@arunsureshkumar Since the dependency has been updated in #202 and #191 , we can close this PR without merging.