Update dependency com.expediagroup:graphql-kotlin-spring-server to v6 - autoclosed #214
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
5.5.0
->6.5.6
⚠ Dependency Lookup Warnings ⚠
Warnings were logged while processing this repo. Please check the Dependency Dashboard for more information.
Release Notes
ExpediaGroup/graphql-kotlin (com.expediagroup:graphql-kotlin-spring-server)
v6.5.6
Compare Source
What's Changed
Full Changelog: ExpediaGroup/graphql-kotlin@6.5.5...6.5.6
v6.5.5
Compare Source
What's Changed
Full Changelog: ExpediaGroup/graphql-kotlin@6.5.3...6.5.5
v6.5.3
Compare Source
What's Changed
Full Changelog: ExpediaGroup/graphql-kotlin@6.5.2...6.5.3
v6.5.2
Compare Source
What's Changed
Full Changelog: ExpediaGroup/graphql-kotlin@6.5.1...6.5.2
v6.5.1
Compare Source
What's Changed
Full Changelog: ExpediaGroup/graphql-kotlin@6.5.0...6.5.1
v6.5.0
Compare Source
What's Changed
This is an special release, that updates
graphql-java
to 20.3, implementing theLightDataFetcher
along with other performance improvements,version update is backwards compatible, making this a candidate for a minor release.
Full Changelog: ExpediaGroup/graphql-kotlin@6.4.1...6.5.0
v6.4.1
Compare Source
What's Changed
Full Changelog: ExpediaGroup/graphql-kotlin@6.4.0...6.4.1
v6.4.0
Minor Changes
v6.3.5
Compare Source
Patch Changes
v6.3.4
Compare Source
Other Changes
v6.3.3
Compare Source
Patch Changes
_FieldSet
Federation v2 fix to 6.x.x branch (#1618)v6.3.2
Compare Source
Other Changes
v6.3.1
Compare Source
Patch Changes
v6.3.0
Compare Source
IMPORTANT: This release fixes Federation v2 support. Earlier versions DO NOT generate valid Federation 2 schema and may fail composition. Federation v1 support was not impacted.
Minor Changes
Patch Changes
Full Changelog: ExpediaGroup/graphql-kotlin@6.2.5...6.3.0
v6.2.5
Compare Source
Patch Changes
v6.2.4
Compare Source
Patch Changes
v6.2.3
Compare Source
Patch Changes
v6.2.2
Compare Source
Patch Changes
Other Changes
v6.2.1
Compare Source
Patch Changes
v6.2.0
Compare Source
Minor Changes
Patch Changes
Other Changes
v6.1.0
Compare Source
Minor Changes
Patch Changes
v6.0.0
Compare Source
🎉 GraphQL Kotlin 6.0.0!
Automatic Coroutine Context Propagation
graphql-kotlin-server
automatically populatesGraphQLContext
map with appropriate coroutine scope. This scope contains coroutine context that was available when processing the incoming HTTP request and is subsequently used by all data fetchers to resolve the underlying fields. Users can customize the coroutine context by providingCoroutineContext::class
entry in custom GraphQL context usingGraphQLContextFactory
.See https://github.com/ExpediaGroup/graphql-kotlin/pull/1349 for details.
Apollo Federation v2 support
Federation v2 is an evolution of the Federation spec to make it more powerful, flexible, and easier to adapt. While v1 and v2 schemas are similar in many ways, Federation v2 relaxes some of the constraints and adds additional capabilities.
See https://github.com/ExpediaGroup/graphql-kotlin/pull/1459 for details.
Update to graphql-java 18
Adds support for applied schema directive. In previous versions, GraphQLDirective represented both a schema definition object as well as individual instances that were applied to a schema or query element. Schema generation logic was updated to continue generating GraphQLDirective schema definitions and then create a corresponding instance of GraphQLAppliedDirective that is applied to a target element.
See https://github.com/ExpediaGroup/graphql-kotlin/pull/1393 for details.
Batching and deduplication of data fetchers for BatchGraphQLRequests
graphql-kotlin-server
can now execute graphql queries concurrently, and because of that we added the capability to use DataLoaders for all queries being executed concurrently, we also added a new custom instrumentation that will dispatch the DataLoaderRegistry when all synchronous data fetchers where dispatched instead of doing it by level simulating what the javascript event loop does with the data loaders and solving these issues:See https://github.com/ExpediaGroup/graphql-kotlin/pull/1419 for details.
More information and examples on our docs
Apollo Automatic Persisted Queries (APQ) support
APQ is a technique created by Apollo to improve GraphQL network performance with zero build-time configuration by sending smaller GraphQL HTTP requests, a smaller request payload reduces bandwidth utilization and speeds up GraphQL client loading times.
See https://github.com/ExpediaGroup/graphql-kotlin/pull/1474 for details.
More information and examples on our docs
Argument deserialization no longer relies on Jackson
Data fetcher argument parsing logic no longer depends on Jackson. Old logic was problematic as arguments passed to data fetchers were already coerced to appropriate type by
graphql-java
but since Jackson was unaware of it, it was resulting in a duplicate deserialization. This caused custom scalar inputs deserialization problems.See https://github.com/ExpediaGroup/graphql-kotlin/pull/1379 for details.
5.x.x Support
Going forward we will only support the
5.x.x
branch for critical security issues or urgent bug fixes.Feedback
As with any open source project, we want to thank the community for using our library and providing valuable feedback and even pull requests. We will continue to support this library and use it in production at @ExpediaGroup, but the goal of the project is still to make GraphQL development easier for everyone. If you have a feature request or question, feel free to start a new discussion, create a new issue or reach out to our public Slack channel.
GitHub has the full list of contributors since we made the 6.0.0 cut.
Major Changes
Minor Changes
Patch Changes
@link
info (#1487) @dariuszkucOther Changes
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.