From bddd683b1e6c1609b32d48d98ccc80cf6a062796 Mon Sep 17 00:00:00 2001
From: Dariusz Kuc <9501705+dariuszkuc@users.noreply.github.com>
Date: Fri, 17 May 2024 11:09:38 -0500
Subject: [PATCH] chore: update federation-jvm to v5.0.0

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.
---
 platform/build.gradle | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/platform/build.gradle b/platform/build.gradle
index 7a677c356..16fe172b4 100644
--- a/platform/build.gradle
+++ b/platform/build.gradle
@@ -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")