chore(deps): update all non-major dependencies #80
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:
2.3.0
->2.3.1
2.2.0
->2.2.1
2.4.1
->2.4.2
2.2.1
->2.2.2
2.4.2
->2.4.3
3.5.0
->3.6.1
3.4.0
->3.5.0
15.7.2
->15.8.0
Release Notes
dotansimha/graphql-code-generator (@graphql-codegen/cli)
v2.3.1
Compare Source
Patch Changes
6002feb
: Fix exports in package.json files for react-native projects8643b3b
]b61dc57
]6002feb
]dotansimha/graphql-code-generator (@graphql-codegen/named-operations-object)
v2.2.1
Compare Source
Patch Changes
6002feb
: Fix exports in package.json files for react-native projects6002feb
]dotansimha/graphql-code-generator (@graphql-codegen/typescript)
v2.4.2
Compare Source
Patch Changes
6002feb
: Fix exports in package.json files for react-native projects6002feb
]dotansimha/graphql-code-generator (@graphql-codegen/typescript-operations)
v2.2.2
Compare Source
Patch Changes
6002feb
: Fix exports in package.json files for react-native projects6002feb
]dotansimha/graphql-code-generator (@graphql-codegen/typescript-resolvers)
v2.4.3
Compare Source
Patch Changes
6002feb
: Fix exports in package.json files for react-native projects6002feb
]apollographql/apollo-server
v3.6.1
Compare Source
apollo-graphql
as intended in v3.6.0. Issue #5981 PR #5981v3.6.0
Compare Source
apollo-server-core
: Studio usage reporting now reports "referenced operations" for fields in addition to "field executions", which can be seen on the Studio Fields page. This new statistic provides visibility into uses of fields that are not executed. It is also more efficient to generate and (for Apollo Gateways) does not require subgraphs to support federated tracing. Additionally, the newfieldLevelInstrumentation
option toApolloServerPluginUsageReporting
allows you to disable field-level tracing on a per-operation basis, and to report weights for operations to allow for estimates of the field execution count even when not all operations are instrumented. Note that the semantics of therequestContext.metrics.captureTraces
field have changed. See the Studio Fields page docs and thefieldLevelInstrumentation
docs for more details. Issue #5708 PR #5956 PR #5963apollo-server-core
: Usage reporting no longer sends a "client reference ID" to Apollo Studio (along with the client name and client version). This little-used feature has not been documented since 2019 and is currently entirely ignored by Apollo Studio. This is technically incompatible as the interfaceClientInfo
no longer has the fieldclientReferenceId
; if you were one of the few users who explicitly set this field and you get a TypeScript compilation failure upon upgrading to v3.6.0, just stop using the field. PR #5890apollo-server-core
: Remove dependency onapollo-graphql
package (by inlining the code which generates usage reporting signatures). That package has not yet been published with agraphql@16
peer dependency, so Apollo Server v3.5 did not fully supportgraphql@16
without overriding peer dependencies. Issue #5941 PR #5955graphql/graphql-js
v15.8.0
Compare Source
v15.8.0 (2021-12-07)
New Feature 🚀
Internal 🏠
2 PRs were merged
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.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR has been generated by WhiteSource Renovate. View repository job log here.