Thanks everyone for your feedback and support during the alpha phase - I'm proud to announce that PostGraphile beta is finally here!
The beta is the final testing phase before we produce the release candidates and ultimately the official version of v4. All of the anticipated breaking changes have been completed during the alpha phase, so the beta should be safe for general usage, including usage in production! Breaking changes from now on will have to be extremely well justified and should only be added in the case of show-stopping issues.
Sign up for announcements here: http://eepurl.com/cYwzUr
I've prepared a full v4 Feature Guide and a v3 → v4 Migration Guide - I encourage everyone to check them out - particularly people coming from PostGraphQL v3.
Aside: I take time off from my paid freelance work to advance the PostGraphile project - I'd love to work on it more, and if you'd like that too why not join my awesome Patreon supporters in contributing to the sustainability of this project!
For those of you who've been using the v4 alpha, the headline changes in this release are below. Please also note that postgraphql@next will not be receiving any more updates so anyone using that should upgrade to postgraphile ASAP.
Breaking changes since the last alpha:
- Requires Node v8.6+
- Internals have been renamed to postgraphile rather than postgraphql, so you may need to scan your codebase if you've been using the non-public interfaces (exports are aliased to their old names); there's also these related changes:
- JWTs now have an audience of 'postgraphile' rather than 'postgraphql'
- Watch schema is now postgraphile_watch rather than postgraphql_watch
DEBUGenvvar now responds to postgraphile rather than postgraphql
New features over the latest alpha:
--legacy-relationsCLI flag for v3 compatibility (see docs)--legacy-json-uuidCLI flag for v3 compatibility (see docs)--no-serverCLI flag (see docs)--cluster-workershighly experimental CLI flag (see docs)- Much faster SQL building performance thanks to a lot of micro-optimisations in
pg-sql2 - Config file support (experimental, undocumented)
- More JWT verification options
- Error message improvements
- Some GraphQL field descriptions have been improved