v3.0 Release

[erikwrede]

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

• association_proxy support #267

• Native support for additional Type Converters #353

• Enable sorting when batching is enabled #355

• Add Filters #357

• feat(async): add support for async sessions #350
  Needs discussion

• [Design Discussion] Additional Type Converters #345

• Add a way to serve custom properties on model classes #103
  Pushed back. Focusing on improving @hybrid_property Support for now.

Documentation ToDos (no release blocker):

• Simplify installation and add tests to examples #194
• Document Hybrid Property Support

[karol-gruszczyk]

Thank you for picking this back up!

[erikwrede]

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.

[bmahler]

@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?

[erikwrede]

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.

[dsully]

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

[ausyau]

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

[ryanpetrello]

Hey folks, cc @erikwrede any updates on when this might graduate from an rc2 to an official 3.0 on PyPI?