Spring/spring-graphql
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Upgrade federation-jvm to 5.0.0

Browse Source 
Closes gh-972

Federation JVM v5 is now using `graphql-java` v22 which caused following breaking changes in behavior

- Apollo `CacheControlInstrumentation` - was using old deprecated instrumentation methods so old version will not work with latest `spring-graphql` version
- there was a breaking change in the schema printing behavior of `@deprecated` information - previously it was always included regardless whether printed schema was filtering  `@deprecated` directive definition. This is an issue for folks relying on self-managed Federation that uses `_service { sdl }` endpoint to obtain subgraph schemas as the supergraph schema would no longer include any deprecation information.
This commit is contained in:
Dariusz Kuc
2024-05-17 11:09:38 -05:00
committed by rstoyanchev
parent 55482cca1a
commit 4e53faf63b
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
platform/build.gradle
View File

@@ -32,7 +32,7 @@ dependencies {
api("jakarta.validation:jakarta.validation-api:3.0.2")
api("jakarta.persistence:jakarta.persistence-api:3.1.0")
api("com.apollographql.federation:federation-graphql-java-support:4.4.0")
api("com.apollographql.federation:federation-graphql-java-support:5.0.0")
api("com.netflix.graphql.dgs.codegen:graphql-dgs-codegen-shared-core:6.1.5")
api("com.google.code.findbugs:jsr305:3.0.2")