-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update dependency apollo-server-express to v2.15.0 #291
Conversation
d17593a
to
5d1b4ec
Compare
Codecov Report
@@ Coverage Diff @@
## master #291 +/- ##
=======================================
Coverage 23.37% 23.37%
=======================================
Files 105 105
Lines 1373 1373
Branches 211 198 -13
=======================================
Hits 321 321
Misses 1052 1052 Continue to review full report at Codecov.
|
5d1b4ec
to
9e65ec2
Compare
9e65ec2
to
719dadd
Compare
719dadd
to
eabbbc9
Compare
eabbbc9
to
4588abb
Compare
Codecov Report
@@ Coverage Diff @@
## master #291 +/- ##
=======================================
Coverage 23.66% 23.66%
=======================================
Files 105 105
Lines 1441 1441
Branches 233 233
=======================================
Hits 341 341
+ Misses 1100 1099 -1
- Partials 0 1 +1
Continue to review full report at Codecov.
|
4588abb
to
0bd539d
Compare
0bd539d
to
09c1033
Compare
4bba32b
to
8fe22e3
Compare
8fe22e3
to
187a69b
Compare
187a69b
to
1ed9700
Compare
This PR contains the following updates:
2.14.2
->2.15.0
Release Notes
apollographql/apollo-server
v2.15.0
Compare Source
apollo-engine-reporting
: Added areportTiming
API to allow trace reporting to be enabled or disabled on a per request basis. The option takes either a boolean or a predicate function that takes aGraphQLRequestContextDidResolveOperation
orGraphQLRequestContextDidEncounterErrors
and returns a boolean. If the boolean is false the request will not be instrumented for tracing and no trace will be sent to Apollo Graph Manager. The default istrue
so all traces will get instrumented and sent, which is the same as the previous default behavior. PR #3918apollo-engine-reporting
: RemovedGraphQLServerOptions.reporting
. It isn't known whether a trace will be reported at the beginning of the request because of the above change. We believe this field was only used internally within Apollo Server; let us know if this is a problem and we can suggest alternatives. Additionally, the fieldrequestContext.metrics.captureTraces
is now initialized later in the request pipeline. PR #3918apollo-engine-reporting
: Make Apollo Server throw if schema reporting is enabled for a gateway or federated service. PR #4246apollo-engine-reporting
: Remove theexperimental_
prefix from schema reporting options, and specifically renameexperimental_schemaReporting
option name toreportSchema
. (The old option names remain functional, but are deprecated.) PR #4236v2.14.5
Compare Source
apollo-engine-reporting
: Make Apollo Server throw if schema reporting is enabled for a gateway or federated service. PR #4246v2.14.4
Compare Source
apollo-engine-reporting
: Add environment variableAPOLLO_SCHEMA_REPORTING
that can enable schema reporting. Ifexperimental__schemaReporting
is set it will override the environment variable. PR #4206apollo-engine-reporting
: The schema reporting URL has been changed to use the new dedicated sub-domainhttps://edge-server-reporting.api.apollographql.com
. PR #4232apollo-server-core
: Though Apollo Server is not affected due to the way it is integrated, in response to an upstream security advisory for GraphQL Playground we have published the same patch on our@apollographql/graphql-playground-html
fork and bumped Apollo Server to use it. Again, this was done out of an abundance of caution since the way that Apollo Server utilizesrenderPlaygroundPage
is not vulnerable as it does not allow per-request Playground configuration that could allow interpolation of user-input. PR #4231v2.14.3
Compare Source
Renovate 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 this update again.
This PR has been generated by WhiteSource Renovate. View repository job log here.