graphene-sqlalchemy icon indicating copy to clipboard operation
graphene-sqlalchemy copied to clipboard

Published 20 hours ago • verified publisher icon graphql-python

v3.0 Release

Open erikwrede opened this issue 2 years ago • 6 comments

This issue will collect ToDos and blockers for this library's 3.0 release.

While graphene==3.0 is already fully supported by the current beta release 3.0.0b3, future beta releases will introduce new features breaking changes included in the full 3.0 release. This issue is WIP; further issues might be added soon.

In progress

  • [ ] #267

  • [x] #353

  • [x] #355

  • [ ] #357

  • [x] #350 Needs discussion

  • [x] #345

  • [x] ~~https://github.com/graphql-python/graphene-sqlalchemy/issues/103~~ Pushed back. Focusing on improving @hybrid_property Support for now.

Documentation ToDos (no release blocker):

  • [ ] #194
  • [ ] Document Hybrid Property Support

erikwrede avatar May 13 '22 12:05 erikwrede

Thank you for picking this back up!

karol-gruszczyk avatar Aug 25 '22 05:08 karol-gruszczyk

Update: Currently working on getting filtering over the finish line. We would highly appreciate some feedback on the PR bringing support for AsyncSession! Please try it out and let us know if you see room for improvement: #350 Hoping to finally have a release candidate roughly at the end of the year.

erikwrede avatar Nov 29 '22 19:11 erikwrede

@erikwrede right now there's no official release that supports python 3.10. Is it worth backporting the 3.10 support to a 2.2.3 release so that folks wanting to use python 3.10+ can upgrade from 2.2.2?

bmahler avatar Jan 25 '23 19:01 bmahler

It really depends on your current setup. If you're not relying on promises, it is a softer path to upgrade to 3.x via the current betas. Currently none of us have the capacity to add the support to 2.x and we are focused on getting 3.0 out. I've been using the 3.0 betas in production for quite some time now and they work great with 3.10 - we are not blocked by any issues on support, but rather waiting on some breaking changes and the filtering feature to be done so we can push them with the full release.

Personally, I recommend to upgrade to 3.0.0b3 or try doing that - because any feedback with that will help us for the full release! Also open to accepting contributions for your 2.x support needs. Please LMK what the scope of that would be.

erikwrede avatar Jan 25 '23 19:01 erikwrede

Would it be possible to put out a 3.0.0b5 with the change to be compatible with SQLAlchemy 2? Thanks.

dsully avatar Sep 07 '23 21:09 dsully

@erikwrede any status updates on when v3.0 will be official?

ausyau avatar Mar 06 '24 20:03 ausyau