v0.10.0

New

• isValidValue() and isValidLiteral() added to Scalar and enum types (#861).
• You can now set a custom default field resolver (#865).
• graphql() may now take a Source object, in addition to the existing support for string (#866).
• graphql() may now take an object with named parameters (#867).
• Partial support for GraphQL subscriptions (#846, #868) (Not yet ready for production use).

Breaking

• Spec compliance: forbid duplicate type definitions (#744).
• Spec compliance: disallow inappropriate coercion of non-Int values to Int (#837).

Fixes

• Ensure GraphQLError stack trace includes error message (#718).
• Fix input coercion to allow null-valued Enums as arguments (#848).
• Fix for fields that are JavaScript keywords (#864).
• Compatibility with Flow v0.47.0 (#878).

v0.9.6

New

• It is now possible to suppress warnings about non-spec compliant names by setting the GRAPHQL_NO_NAME_WARNING environment variable. This may be useful when working with legacy schemas.

v0.9.5

New:

• Much improved Flow types from the experimental %checks type (#695)
• Allow passing a custom TypeInfo instance to validate() (#834)
• Exported getVisitFn for building custom composite visitors. (#807)

Fixes:

• Allow Enum internal values to be false, null, and undefined (#836)

v0.9.4

New:

• All validation rules are now exported directly (#808)

Fixes:

• Fix flow issue with constructing new GraphQLError() (#829)

Spec Compliance:

• Now throws error when building Enum with reserved words (#812)
• Now throws error when building Union with multiple of the same type (#813)
• Now throws error when building Object type implementing the same Interface more than once (#728)

v0.9.3

Fixes

• Eliminate false positives reported by findArgChanges (#783).

v0.9.2

Breaking

• Remove ambiguity in isLeafType check: it no longer performs named type unwrapping and is consistent with the other isCompositeType/isAbstractType checks (#697).

New

• Make wording in error messages more consistent (#767).
• Allow deprecated fields/values to be extended (#755).
• Validation messages about names starting with double underscores are now use console.warn rather than console.error (#717).
• Improved the error message for undefined field config (#702).
• The findBreakingChanges validation now reports breaking changes made to arguments (#701).

Internal

• Performance improvements to the separateOperations module (#710).
• Improvements to Flow checking (#699) and type safety (#698).

v0.9.1

Fixes

• Downgrade error to warning for non-spec-compliant use of non-meta fields starting with __ (#692).
• Workaround for problem in some environments with reserved literals (such as default) being used as properties (#693).

v0.9.0

New:

• Added isNamedType() and assertNamedType() #589
• Default field resolvers now get full execution info as a third argument #615
• ObjectType.isTypeOf() and InterfaceType.resolveType() may now return Promises #631
• Support and fixes for flow type v0.38 #671
• Added TypeInfo.getEnumValue() and EnumType.getValue(name) #674
• Added findDeprecatedUsages() #676

Fixes:

• Enforce spec that no non-meta field may start with "__" #600 (Potentially breaking for existing non-compliant uses).
• isValidJSValue() reports if coercion results in error #602
• Executor throws friendlier error if no document is provided #614
• Fixed import circular dependency, improving compressed builds #644

v0.8.2

New:

• assertXXXType() functions help ensure type-correct code using graphql (#570)
• Added toJSON() and inspect() methods on all GraphQL types for easier debugging (#578)
• ValidationContext types are exported (a17256b)

Fixes:

• Differentiate between input values with no default and with null default (#569)
• Improvements to Flow types in field resolvers (#573, #575, #577)

v0.8.1

Fixes:

• Supports Flow v0.35
• GraphQL parser now returns clearer error messages (07cc624)