fix(deps): update apollo graphql packages to v3.6.2 #8961
Merged
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.6.1
->3.6.2
3.6.1
->3.6.2
3.6.1
->3.6.2
Release Notes
apollographql/apollo-server
v3.6.2
Compare Source
apollo-server-env
: Update dependency onnode-fetch
to require v2.6.7 rather than v2.6.1. This includes the fix to CVE-2022-0235, a vulnerability where credentials sent along with a request could be sent to a different origin if the fetched URL responds with an attacker-controlled HTTP redirect. This is the default fetcher used byapollo-datasource-rest
, usage reporting, schema reporting, and@apollo/gateway
in versions prior to v0.46.0. We do not believe that the way that this is used by usage reporting or schema reporting is vulnerable to the exploit, but if you useapollo-datasource-rest
in such a way that the servers you talk to might serve a surprising redirect, this upgrade would be helpful. Note that to ensure you're using the appropriate version ofapollo-server-env
withapollo-datasource-rest
, you need to be using v3.5.1 of that package. (We plan to separate the release process ofapollo-datasource-rest
from Apollo Server soon so that it can have a more reasonable changelog.) If upgrading to this version is challenging, you can also work around this by ensuring that[email protected]
is the version used in your project, or by specifying afetcher
explicitly to your older Gateway, REST datasource, etc.apollo-server-core
: ThetypeDefs
,resolvers
, andparseOptions
constructor arguments are passed directly through tomakeExecutableSchema
from@graphql-tools/schema
if provided. Now their TypeScript type definitions come directly from that package so that any types accepted by that package can be provided. PR #5978apollo-server-fastify
: Drop dependency onfast-json-stringify
. PR #5988apollo-server-azure-functions
: Update TypeScript types package@azure/functions
from v1 to v3 and change it to a dev dependency. (We were advised to change it to a dev dependency by the authors of the package; if this turns out to be problematic we can revert this part of the change. They also do not believe this is a backwards-incompatible change despite the major version bump; this package does a major version bump when the underlying Azure Functions runtime has a major version bump.) PR #5919Configuration
📅 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.