Skip to content

Bugfixes, Docker, and lots of documentation improvements
Compare
Choose a tag to compare
@benjie benjie released this 18 Jul 08:12
· 10509 commits to main since this release
v3.3.0
7272d61

This release of v3 contains many fixes and improvements; plus it introduces the Docker image maintained by @angelosarto. There are a couple changes that may impact security depending on how you use PostGraphQL so please pay extra attention to the items in bold below.

ANNOUNCEMENT: v4 is just around the corner - it's a ground-up rebuild of the GraphQL schema generation to improve performance and support plugins to allow you to extend or modify the generated GraphQL schema to your hearts content! There's a few minor breaking changes but for most people it should be pretty much a drop-in replacement. I really need help testing it, and you can track progress on #506

Features

  • GraphiQL now uses credentials: 'same-origin' (#436)
  • Adds support for mutations that return void (#435)
  • Set 401 status on expired token (#472)
  • Warn if jwtSecret is set but jwtPgTypeIdentifier is not (#466 and #500)
  • --jwt-role option to extract pgRole from arbitrary JWT path (#480)
  • Generate Docker image (#496)

Fixes

  • Documentation fixes (#423, #477, #497, #498, #503, and #507)
  • Fixes processing of command line options --jwt-secret and --jwt-audiences (#434)
  • Fixes building when path has spaces in (#441)
  • Clarify computed column function criteria (#462)
  • Document pgSettings option (#451)
  • Don't throw an error when an Authorization header is present if no --jwt-secret specified (assume the application is handling it) (#437)
  • Better performance for paginators by utilising CTEs to work around to_json performance issues (#396)
  • JWT type names can now contain numbers 0-9, not just 1 and 2 (#511)

Contributors

I want to take this opportunity to thank @calebmer for all his work over the past couple years and for bringing this project to where it is today! He has moved on to working on the Flow team at Facebook, leaving some awfully big shoes to fill - as the new primary maintainer I hope that I can fill them with anywhere near the eloquence that Caleb had!

I'd also like to thank the (many) contributors of this release, including:

If you want to chat with us, join us on gitter: https://gitter.im/calebmer/postgraphql

Assets 2
Loading