Skip to content

Releases: graphql-python/graphene-django

v3.2.1

09 Apr 00:38
d69c905
Compare
Choose a tag to compare

What's Changed

New Contributors

Full Changelog: v3.2.0...v3.2.1

v3.2.0

20 Dec 10:22
4d0484f
Compare
Choose a tag to compare

What's Changed

New Contributors

Full Changelog: v3.1.6...v3.2.0

v3.1.6

20 Dec 09:44
3a64994
Compare
Choose a tag to compare

What's Changed

New Contributors

Full Changelog: v3.1.5...v3.1.6

v3.1.5

09 Aug 22:12
4ac3f3f
Compare
Choose a tag to compare

What's Changed

New Contributors

Full Changelog: v3.1.3...v3.1.5

v3.1.3

18 Jul 12:14
2fafa88
Compare
Choose a tag to compare

What's Changed

  • Update the path to GraphQL Server Specification for Relay by @rapsealk in #1432
  • Add JSONField back to graphene_django.compat module for backwards compatibility by @sjdemartini in #1429

New Contributors

Full Changelog: v3.1.2...v3.1.3

v3.1.2

17 Jun 06:41
e950164
Compare
Choose a tag to compare

What's Changed

New Contributors

Full Changelog: v3.1.1...v3.1.2

v2.16.0

26 May 20:10
f386251
Compare
Choose a tag to compare

What's Changed

New Contributors

Full Changelog: v2.15.0...v2.16.0

v3.1.1

24 May 13:10
ebf4943
Compare
Choose a tag to compare

What's Changed

🎉 * Add support for Python 3.11 by @ulgens in #1365 🎉

New Contributors

Full Changelog: v3.0.2...v3.1.0

v3.0.2

03 May 09:16
Compare
Choose a tag to compare

What's Changed

This is a minor release addresses the N+1 problem caused by #1315.

WARNING
Just a heads up for folks who use get_queryset as an auth layer. If you need that, you can stick with versions between >=3.0.0b9 and <3.0.2 for now. Feel free to suggest a different way that won't lead to those pesky N+1 SQL query issues.

Full Changelog: 3.0.2...v3.0.2

v3.0.1

29 Apr 17:27
34cc860
Compare
Choose a tag to compare

What's Changed

New Contributors

Full Changelog: v3.0.0...v3.0.1