This repository was archived by the owner on Dec 19, 2023. It is now read-only.
chore(deps): update graphql java (ignoring snapshot builds) to v18.1 #815
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/graphql-java-(ignoring-snapshot-builds)
branch
from
4593c72 to
9363dd2
Compare
|
Kudos, SonarCloud Quality Gate passed!
|
BlasiusSecundus
deleted the
renovate/graphql-java-(ignoring-snapshot-builds)
branch
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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:
18.0->18.118.0->18.1Release Notes
graphql-java/graphql-java-extended-scalars
v18.1What's Changed
New Contributors
Full Changelog: graphql-java/graphql-java-extended-scalars@v18.0...v18.1
graphql-java/graphql-java
v18.1This bug fix release contains an important fix
https://github.com/graphql-java/graphql-java/pull/2773
The latest 18.0 version of graphql-java changed the way raw values are resolved to canonical values.
However this revealed a bug in MaxQueryXXX instrumentation where invalid values (null being present for non nullable input values) caused an exception rather than generating a graphql error. This is not a behavior we intended.
The bug is only present if you use
graphql.analysis.MaxQueryDepthInstrumentationandgraphql.analysis.MaxQueryDepthInstrumentationWhat's Changed
TypeRuntimeWiring.enumValues()error message by @martinbonnin in https://github.com/graphql-java/graphql-java/pull/2782AstPrinterto print field descriptions by @david-castaneda in https://github.com/graphql-java/graphql-java/pull/2808New Contributors
Full Changelog: graphql-java/graphql-java@v18.0...v18.1
Configuration
📅 Schedule: 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 these updates again.
This PR has been generated by WhiteSource Renovate. View repository job log here.