v0.9.0

• Update protobuf-java to 3.19.4 (#141)
• Add support for graphql-java GraphQLContext (#138). Many thanks to @dariuszuc for the awesome contribution 💙

v0.8.0

This release adds support for the @CacheControl directive in the form of a graphql-java instrumentation class, matching the behavior of the apollo-server's built-in cache control plugin. (#133)

v0.7.0

This is an upgrade release for graphql-java v17. This release is incompatible with earlier graphql-java versions due to backwards-incompatible changes in their SchemaPrinter.

Upgrades:

• graphql-java to 17.3.

v0.6.5

Enhancements:

• Split out the HTTPRequestHeaders interface into its own artifact federation-graphql-java-support-api. This allows third-party libraries to have their context implement this interface without pulling in all the dependencies of federation-graphql-java-support.
• Allow providing a function to FederatedTracingInstrumentation.Options to decide whether to enable tracing based on the ExecutionInput and its context. This is useful if a third-party library does not wish to implement HTTPRequestHeaders.

v0.6.4

Upgrades:

• Spring Boot libraries to 2.3.6.RELEASE.
• GraphQL Java Kickstart libraries to 11.0.0.

Enhancements:

• Add a GraphQL Java Tools microservice example.

v0.6.3

This release marks the switch of our package hosting from JCenter to Maven Central, as JCenter will be shutting down over the course of the next year. This release contains no code changes, and is primarily to support users who wish to remove any dependencies on JCenter.

v0.6.2

Bugfixes:

• Fix bug where the @key directive is not marked repeatable, which results in API call failures due to new assertions introduced in graphql-java v16.

v0.6.1

Bugfixes:

• Fix bug where Federation.transform() would remove all query type fields from a schema with query type extensions but an empty query type.

v0.6.0

This is an upgrade release for graphql-java v16. This release is incompatible with earlier graphql-java versions due to backwards-incompatible changes in their API.

Note that if your schema has an empty query type/no query type and you pass a GraphQLSchema object to this library, your GraphQLSchema will no longer build in graphql-java v16 due to a new validation. To work around this, you can add a dummy field to your GraphQLSchema's query type, and then pass queryTypeShouldBeEmpty as true to Federation.transform(). The output schema won't contain the dummy field, nor will it be visible to the gateway. If you instead pass a different representation of a schema to Federation.transform() (e.g. a string), you don't have to do anything; this library will handle the issue internally.

Upgrades:

• graphql-java to 16.1.

v0.5.0

This is an upgrade release for graphql-java v15. This release is incompatible with earlier graphql-java versions due to backwards-incompatible changes in their SchemaPrinter.

Upgrades:

• graphql-java to 15.0.