Hello!

Mark your calendars for the upcoming GraphQL-Ruby Hack Day! It will be held on Friday, August 25, in Amsterdam. You can RSVP on the Meetup page and join the discussion on the planning repo. If you can't join for the hack day, consider attending GraphQL-Themed Talks and Drinks in the evening. Special thanks to the organizers, @emilebosch, @esjee, and @willianvdv for making this happen! I hope to see some of you there :) 


Meanwhile, graphql is up to 1.6.6! The 1.6.x version includes:

• Multiplexing, for running many queries concurrently (eg, Apollo batching), which graphql-batch support merged on master.
• validate: false, for skipping validation when you know that a query is correct and safe, but you want more speed.
• GraphQL::RakeTask for managing .graphql or .json dumps of the schema in your project. (Now with sorted output!)
• Schema-level default max_page_size for Relay connections.
• Interface- and Union-level resolve_type functions  so you can provide fine-grained type resolution
• Other features, changes and fixes, so check the CHANGELOG for full details!

graphql-pro has had many improvements as well: 

• Lots of authorization improvements, including default auth level, scope-based auth for ActiveRecord, and custom hooks for unauthorized objects
• OperationStore, a persisted query database for ActiveRecord. You can mount OperationStore in your Rails app, then use the JavaScript client tooling to use persisted queries with Relay, Apollo client or plain JS. OperationStore serves a UI for managing its contents:
  
  
• Other improvements and fixes (CHANGELOG)

A few other interesting projects caught my eye recently: 

- GraphQL::SchemaComparator finds breaking changes between to schemas (by @xuorig) 
- Life of a GraphQL Query: Lexing/Parsing describes clearly the first few steps in query execution (by @cjoudrey)


Want to know what's coming next? Check out the hack day topics to see what's on our radar! May all your schema changes be non-breaking, 

- Robert Mosolgo