fix(deps): update apollo graphql packages #7777
Merged
+8
−8
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:
3.13.5
->3.13.7
4.11.3
->4.12.0
Release Notes
apollographql/apollo-client (@apollo/client)
v3.13.7
Compare Source
Patch Changes
#12540
0098932
Thanks @phryneas! - Refactor: Move notification scheduling logic fromQueryInfo
toObservableQuery
#12540
0098932
Thanks @phryneas! - Refactored cache emit logic for ObservableQuery. This should be an invisible change.v3.13.6
Compare Source
Patch Changes
cdc55ff
Thanks @phryneas! - keep ObservableQuery created by useQuery non-active before it is first subscribedapollographql/apollo-server (@apollo/server)
v4.12.0
Compare Source
Minor Changes
89e3f84
Thanks @clenfest! - Adds a new graphql-js validation rule to reject operations that recursively request selections above a specified maximum, which is disabled by default. Use configuration optionmaxRecursiveSelections=true
to enable with a maximum of 10,000,000, ormaxRecursiveSelections=<number>
for a custom maximum. Enabling this validation can help avoid performance issues with configured validation rules or plugins.Patch Changes
2550d9f
Thanks @slagiewka! - Add return after sending 400 response in doubly escaped JSON parser middlewareConfiguration
📅 Schedule: Branch creation - "before 8am every weekday,every weekend" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR was generated by Mend Renovate. View the repository job log.