v0.9.3

• Fix issue where containers would forget variables previously set with setVariables, specifically when using array/object variables (closes #1357).
• Add Relay.disableQueryCaching API (closes #754), which may be useful running Relay in a server context.
• Suppress spurious warning when using IGNORE as a rangeBehavior (closes #1337).
• Use a more accurate query name based on current route in RelayQuery.cloneWithRoute (see commit de954992), making logging and analytics that relies on query names more accurate.
• RelayNetworkDebug now prints an estimated request size (see commit b94ba409).
• Preserve type information in callsToGraphQL/callsFromGraphQL, fixing issues with null (closes #1256).
• Fix a subtle ordering issue by writing linked IDs before traversing plural linked fields; this solves a rare edge case where data could be written to the wrong ID given a recursive query (see commit be45692f).
• Expose injectCacheManager on RelayEnvironment (closes #1320).
• Expose Relay.QueryConfig (closes #1279).
• Ensure that instances of GraphQLRange get correctly deserialized (closes #1293).
• Fix a case where tracked nodes would incorrectly trigger a refetch of plural fields with null linked field children (see commit 5c08fd60).
• Make error-handling consistent between 200 status responses with errors attributes and non-200 responses (#1163).
• Warn when producing a diff query involving a client: ID, necessitating the use of a path when a refetchable ID would be preferable in order to produce a correct result (commit 928411df).