fix(deps): update apollo graphql packages (major) #9662
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.
Coming soon: The Renovate bot (GitHub App) will be renamed to Mend. PRs from Renovate will soon appear from 'Mend'. Learn more here.
This PR contains the following updates:
^3.12.2
->^4.0.0
^4.10.0
->^5.0.0
Release Notes
apollographql/apollo-client (@apollo/client)
v4.0.5
Compare Source
Patch Changes
e2fc385
Thanks @phryneas! - Fix an invariance type error in theMockedResponse
type.v4.0.4
Compare Source
Patch Changes
#12892
db8a04b
Thanks @jerelmiller! - Prevent unhandled rejections from the promise returned by calling themutate
function from theuseMutation
hook.#12899
5352c12
Thanks @phryneas! - Fix an issue wheninvariant
is called by external libraries when no dev error message handler is loaded.#12895
71f2517
Thanks @jerelmiller! - SupportskipToken
withuseQuery
to provide a more type-safe way to skip query execution.Note: this change is provided as a patch within the 4.0 minor version because the changes to TypeScript validation with required variables in version 4.0 made using the
skip
option more difficult.#12900
c0d5be7
Thanks @phryneas! - Use named exportequal
instead of default from"@​wry/equality"
v4.0.3
Compare Source
Patch Changes
#12887
6f6ca47
Thanks @phryneas! - Fix accidental deep re-export from/react
out of/react/internals
#12890
019b422
Thanks @jerelmiller! - Ensure thevariables
option foruseMutation
provides proper IntelliSense suggestions.v4.0.2
Compare Source
Patch Changes
56fac52
Thanks @phryneas! - restoregetMemoryInternals
access in dev buildsv4.0.1
Compare Source
Patch Changes
#12876
b00f231
Thanks @phryneas! - Fix CJS build output forinvariantErrorCodes
#12866
0d1614a
Thanks @jerelmiller! - ExportisNetworkStatusInFlight
from@apollo/client/utilities
. AddisNetworkStatusSettled
to@apollo/client/utilities
and re-export it from@apollo/client
with a deprecation.v4.0.0
Compare Source
apollographql/apollo-server (@apollo/server)
v5.0.0
Compare Source
BREAKING CHANGES
Apollo Server v5 has very few breaking API changes. It is a small upgrade focused largely on adjusting which versions of Node.js and Express are supported.
Read our migration guide for more details on how to update your app.
graphql
library older thanv16.11.0
. (Apollo Server 4 supportsgraphql
v16.6.0
or later.) Upgradegraphql
before upgrading Apollo Server.@apollo/server/express4
, or you could import it from the separate package@as-integrations/express4
. In Apollo Server 5, you must import it from the separate package. You can migrate your server to the new package before upgrading to Apollo Server 5. (You can also use@as-integrations/express5
for a middleware that works with Express 5.)fetch
implementation for HTTP requests by default, instead of thenode-fetch
npm package. If your server uses an HTTP proxy to make HTTP requests, you need to configure it in a slightly different way. See the migration guide for details.startStandaloneServer
no longer uses Express. This is mostly invisible, but it does set slightly fewer headers. If you rely on the fact that this server is based on Express, you should explicitly use the Express middleware.@defer
and@stream
(which requires using a pre-release version ofgraphql
v17) now explicitly only works with version17.0.0-alpha.2
ofgraphql
. Note that this supports the same incremental delivery protocol implemented by Apollo Server 4, which is not the same protocol in the latest alpha version ofgraphql
. As this support is experimental, we may switch over from "onlyalpha.2
is supported" to "only a newer alpha or final release is supported, with a different protocol" during the lifetime of Apollo Server 5.variables
map for a variable declared in the operation as aString
) with a 400 status code, indicating a client error. This is also the behavior of Apollo Server 3. Apollo Server 4 mistakenly responds to these requests with a 200 status code by default; we recommended the use of thestatus400ForVariableCoercionErrors: true
option to restore the intended behavior. That option now defaults to true.precomputedNonce
option to landing page plugins (which was only non-deprecated for 8 days) has been removed.Patch Changes
There are a few other small changes in v5:
#8076
5b26558
Thanks @valters! - Fix some error logs to properly calllogger.error
orlogger.warn
withthis
set. This fixes errors or crashes from logger implementations that expectthis
to be set properly in their methods.#7515
100233a
Thanks @trevor-scheer! - ApolloServerPluginSubscriptionCallback now takes afetcher
argument, like the usage and schema reporting plugins. The default value is Node's built-in fetch.Updated dependencies [
100233a
]:Configuration
📅 Schedule: Branch creation - "before 7am on Tuesday,before 7am on Wednesday" in timezone Australia/Sydney, Automerge - 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 was generated by Mend Renovate. View the repository job log.