Federation JVM v5 is now using graphql-java v22 which had 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.
Federation JVM v5 is now using
graphql-javav22 which had following breaking changes in behaviorCacheControlInstrumentation- was using old deprecated instrumentation methods so old version will not work with latestspring-graphqlversion@deprecatedinformation - previously it was always included regardless whether printed schema was filtering@deprecateddirective 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.