-
Notifications
You must be signed in to change notification settings - Fork 23
fix(deps): update apollo graphql packages #289
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
base: main
Are you sure you want to change the base?
Conversation
|
|
You can download the latest build of the extension for this PR here: To install the extension, download the file, unzip it and install it in VS Code by selecting "Install from VSIX..." in the Extensions view. Alternatively, run code --install-extension vscode-apollo-0.0.0-build-1764001731.pr-289.commit-e0eb3d7.vsix --forcefrom the command line. For older builds, please see the edit history of this comment. |
e2af702 to
808ade3
Compare
808ade3 to
8496bf2
Compare
4110dca to
7398af0
Compare
7398af0 to
274ceb9
Compare
1df153b to
5727d61
Compare
5727d61 to
8ca14f6
Compare
ce1430e to
f52debb
Compare
2033424 to
d45a5e8
Compare
b0f976f to
b5c1a37
Compare
0274d81 to
b75a9a0
Compare
04e4aea to
1b4f1aa
Compare
19bdd1c to
50fe276
Compare
9989a69 to
85da1a4
Compare
85da1a4 to
bdcbc8e
Compare
f35bc91 to
d52d026
Compare
d52d026 to
fc3bfcb
Compare
fc3bfcb to
22c8309
Compare
This PR contains the following updates:
3.12.3->3.14.04.20.1->4.21.112.9.3->2.12.1v2.2.0->v2.8.2Release Notes
apollographql/apollo-client (@apollo/client)
v3.14.0Compare Source
Minor Changes
#12752
8b779b4Thanks @jerelmiller! - Add deprecations and warnings to remaining APIs changed in Apollo Client 4.0.#12746
0bcd2f4Thanks @jerelmiller! - Add warnings and deprecations for options and methods for all React APIs.#12751
567cad8Thanks @jerelmiller! - Add@deprecatedtags to all properties returned from any query API (e.g.client.query,observableQuery.refetch, etc.),client.mutate, andclient.subscribethat are no longer available in Apollo Client 4.0.#12746
0bcd2f4Thanks @jerelmiller! - AddpreloadQuery.toPromise(queryRef)as a replacement forqueryRef.toPromise().queryRef.toPromise()has been removed in Apollo Client 4.0 in favor ofpreloadQuery.toPromiseand is now considered deprecated.#12736
ea89440Thanks @jerelmiller! - Add deprecations and deprecation warnings forApolloClientoptions and methods.#12763
5de6a3dThanks @jerelmiller! - Version bump only to release latest asrc.#12459
1c5a031Thanks @jerelmiller! - ResetaddTypenameTransformandfragmentscaches when callingcache.gc()only whenresetResultCacheistrue.#12743
92ad409Thanks @jerelmiller! - Add deprecations and warnings foraddTypenameinInMemoryCacheandMockedProvider.#12743
92ad409Thanks @jerelmiller! - Add deprecations and warnings forcanonizeResults.#12751
567cad8Thanks @jerelmiller! - Warn when using astandbyfetch policy withclient.query.Patch Changes
ecf3de1Thanks @phryneas! - Prevent field policies from overwriting/merging into supertype field policies.v3.13.9Compare Source
Patch Changes
32c9aa9Thanks @phryneas! - Fix a possible race condition on queries that were reobserved before they were subscribed to the first time.v3.13.8Compare Source
Patch Changes
c19d415Thanks @thearchitector! - Fix in-flight multipart urql subscription cancellationv3.13.7Compare Source
Patch Changes
#12540
0098932Thanks @phryneas! - Refactor: Move notification scheduling logic fromQueryInfotoObservableQuery#12540
0098932Thanks @phryneas! - Refactored cache emit logic for ObservableQuery. This should be an invisible change.v3.13.6Compare Source
Patch Changes
cdc55ffThanks @phryneas! - keep ObservableQuery created by useQuery non-active before it is first subscribedv3.13.5Compare Source
Patch Changes
12c8d06Thanks @jerelmiller! - Fix an issue where acache-firstquery would return the result for previous variables when a cache update is issued after simultaneously changing variables and skipping the query.v3.13.4Compare Source
Patch Changes
fee9368Thanks @jorenbroekema! - Use import star fromrehacktto prevent issues with importing named exports from external CJS modules.v3.13.3Compare Source
Patch Changes
#12362
f6d387cThanks @jerelmiller! - Fixes an issue where callingobservableQuery.getCurrentResult()when theerrorPolicywas set toallwould return thenetworkStatusasNetworkStatus.readywhen there were errors returned in the result. This has been corrected to reportNetworkStatus.error.This bug also affected the
useQueryanduseLazyQueryhooks and may affect you if you check fornetworkStatusin your component.v3.13.2Compare Source
Patch Changes
#12409
6aa2f3eThanks @phryneas! - To mitigate problems when Apollo Client ends up more than once in the bundle, some unique symbols were converted intoSymbol.forcalls.#12392
644bb26Thanks @Joja81! - Fixes an issue where the DeepOmit type would turn optional properties into required properties. This should only affect you if you were using the omitDeep or stripTypename utilities exported by Apollo Client.#12404
4332b88Thanks @jerelmiller! - ShowNaNrather than converting tonullin debug messages fromMockLinkfor unmatchedvariablesvalues.v3.13.1Compare Source
Patch Changes
#12369
bdfc5b2Thanks @phryneas! -ObervableQuery.refetch: don't refetch withcache-and-network, swich tonetwork-onlyinstead#12375
d3f8f13Thanks @jerelmiller! - Export theUseSuspenseFragmentOptionstype.v3.13.0Compare Source
Minor Changes
#12066
c01da5dThanks @jerelmiller! - Adds a newuseSuspenseFragmenthook.useSuspenseFragmentsuspends untildatais complete. It is a drop-in replacement foruseFragmentwhen you prefer to use Suspense to control the loading state of a fragment. See the documentation for more details.#12174
ba5cc33Thanks @jerelmiller! - Ensure errors thrown in theonCompletedcallback fromuseMutationdon't callonError.#12340
716d02eThanks @phryneas! - Deprecate theonCompletedandonErrorcallbacks ofuseQueryanduseLazyQuery.For more context, please see the related issue on GitHub.
#12276
670f112Thanks @Cellule! - Provide a more type-safe option for the previous data value passed toobservableQuery.updateQuery. Using it could result in crashes at runtime as this callback could be called with partial data even though its type reported the value as a complete result.The
updateQuerycallback function is now called with a new type-safepreviousDataproperty and a newcompleteproperty in the 2nd argument that determines whetherpreviousDatais a complete or partial result.As a result of this change, it is recommended to use the
previousDataproperty passed to the 2nd argument of the callback rather than using the previous data value from the first argument since that value is not type-safe. The first argument is now deprecated and will be removed in a future version of Apollo Client.#12174
ba5cc33Thanks @jerelmiller! - Reject the mutation promise if errors are thrown in theonCompletedcallback ofuseMutation.Patch Changes
#12276
670f112Thanks @Cellule! - Fix the return type of theupdateQueryfunction to allow forundefined.updateQueryhad the ability to bail out of the update by returning a falsey value, but the return type enforced a query value.#12296
2422df2Thanks @Cellule! - Deprecate optionignoreResultsinuseMutation.Once this option is removed, existing code still using it might see increase in re-renders.
If you don't want to synchronize your component state with the mutation, please use
useApolloClientto get your ApolloClient instance and callclient.mutatedirectly.#12338
67c16c9Thanks @phryneas! - In case of a multipart response (e.g. with@defer), query deduplication willnow keep going until the final chunk has been received.
#12276
670f112Thanks @Cellule! - Fix the type of thevariablesproperty passed as the 2nd argument to thesubscribeToMorecallback. This was previously reported as thevariablestype for the subscription itself, but is now properly typed as the queryvariables.v3.12.11Compare Source
Patch Changes
#12351
3da908bThanks @jerelmiller! - Fixes an issue where the wrongnetworkStatusandloadingvalue was emitted fromobservableQuerywhen callingfetchMorewith ano-cachefetch policy. ThenetworkStatusnow properly reports asreadyandloadingasfalseafter the result is returned.#12354
a24ef94Thanks @phryneas! - Fix missingmain.d.ctsfilev3.12.10Compare Source
Patch Changes
#12341
f2bb0b9Thanks @phryneas! -useReadQuery/useQueryRefHandlers: Fix a "hook order" warning that might be emitted in React 19 dev mode.#12342
219b26bThanks @phryneas! - Addgraphql-ws^6.0.3as a validpeerDependencyv3.12.9Compare Source
Patch Changes
#12321
daa4f33Thanks @jerelmiller! - Fix type ofextensionsinprotocolErrorsforApolloErrorand theonErrorlink. According to the multipart HTTP subscription protocol, fatal tranport errors follow the GraphQL error format which requireextensionsto be a map as its value instead of an array.#12318
b17968bThanks @jerelmiller! - AllowRetryLinkto retry an operation when fatal transport-level errors are emitted from multipart subscriptions.v3.12.8Compare Source
Patch Changes
#12292
3abd944Thanks @phryneas! - Remove unused dependencyresponse-iterator#12287
bf313a3Thanks @phryneas! - Fixes an issue whereclient.watchFragment/useFragmentwith@includescrashes when a separate cache update writes to the conditionally included fields.v3.12.7Compare Source
Patch Changes
#12281
d638ec3Thanks @jerelmiller! - Make fatal tranport-level errors from multipart subscriptions available to the error link with theprotocolErrorsproperty.#12281
d638ec3Thanks @jerelmiller! - Fix the array type for theerrorsfield on theApolloPayloadResulttype. This type was always in the shape of the GraphQL error format, per the multipart subscriptions protocol and never a plain string or a JavaScript error object.v3.12.6Compare Source
Patch Changes
#12267
d57429dThanks @jerelmiller! - Maintain theTDatatype when used withUnmaskedwhenTDatais not a masked type generated from GraphQL Codegen.#12270
3601246Thanks @jerelmiller! - Fix handling of tagged/branded primitive types when used as scalar values withUnmasked.v3.12.5Compare Source
Patch Changes
#12252
cb9cd4eThanks @jerelmiller! - Changes the default behavior of theMaybeMaskedtype to preserve types unless otherwise specified. This change makes it easier to upgrade from older versions of the client where types could have unexpectedly changed in the application due to the default of trying to unwrap types into unmasked types. This change also fixes the compilation performance regression experienced when simply upgrading the client since types are now preserved by default.A new
modeoption has now been introduced to allow for the old behavior. See the next section on migrating if you wish to maintain the old default behavior after upgrading to this version.Migrating from <= v3.12.4
If you've adopted data masking and have opted in to using masked types by setting the
enabledproperty totrue, you can remove this configuration entirely:If you prefer to specify the behavior explicitly, change the property from
enabled: true, tomode: "preserveTypes":declare module "@​apollo/client" { interface DataMasking { - enabled: true + mode: "preserveTypes" } }If you rely on the default behavior in 3.12.4 or below and would like to continue to use unmasked types by default, set the
modetounmask:v3.12.4Compare Source
Patch Changes
4334d30Thanks @charpeni! - Fix an issue withrefetchQuerieswhere comparingDocumentNodes internally by references could lead to an unknown query, even though theDocumentNodewas indeed an active query—with a different reference.apollographql/apollo-client-devtools (@apollo/client-devtools-vscode)
v4.21.11Compare Source
v4.21.10Compare Source
Patch Changes
17cfb5dThanks @github-actions! - add error codes for new Apollo Client versionv4.21.9Compare Source
Patch Changes
83210f7Thanks @github-actions! - add error codes for new Apollo Client versionv4.21.8Compare Source
Patch Changes
c66090bThanks @github-actions! - add error codes for new Apollo Client versionv4.21.7Compare Source
Patch Changes
c8544b5Thanks @github-actions! - add error codes for new Apollo Client versionv4.21.6Compare Source
Patch Changes
8a74f35Thanks @github-actions! - add error codes for new Apollo Client versionv4.21.5Compare Source
v4.21.4Compare Source
Patch Changes
ab5738bThanks @github-actions! - add error codes for new Apollo Client versionv4.21.3Compare Source
Patch Changes
5e2645aThanks @github-actions! - add error codes for new Apollo Client versionv4.21.2Compare Source
Patch Changes
0302538Thanks @braineo! - fix calling client.stop twice causing app crashing by checking if handler exist before sending tab commandv4.21.1Compare Source
Patch Changes
c0f4446Thanks @github-actions! - add error codes for new Apollo Client versionv4.21.0Compare Source
Minor Changes
b935cf8Thanks @jerelmiller! - Add a memory panel to monitor internal Apollo Client caches.v4.20.2Compare Source
Patch Changes
88ef65dThanks @jerelmiller! - add error codes for new Apollo Client versionapollographql/federation (@apollo/subgraph)
v2.12.1Compare Source
Patch Changes
09e596e6a0c753071ca822e84f525d73ada395cf,ac1ed2946c48e0fef4b413b192d8c5fbdb2370ae]:v2.12.0Compare Source
Minor Changes
Patch Changes
When a
GraphQLScalarTyperesolver is provided tobuildSubgraphSchema(), omitted configuration options in theGraphQLScalarTypeno longer cause the corresponding properties in the GraphQL document/AST to be cleared. To explicitly clear these properties, usenullfor the configuration option instead. (#3287)Updated dependencies [
3e2b0a8569a9fe46726182887ed0b4bfc0b52468,bb4614d338ae03bac51a5fc2439590f172c4e54d,99f2da21de88f9ad9a32ee7ed64b2d4a92887b40,468f27842608f4e390cfc88bc7e6b4b0945f95ff,3fd5157b309f1d3439b2d87c67b0601fb246d04c,b734ea04d118db09cf6077fdd968c8f04a96327a,4bda3a498eba36e187dfd9ae673eca12d3f3502c,e7e67579908d5cd2fa6fe558228dffe4808cd98d,faea2d1174d80593264f2227cfde9a2ba1a59b96,97b9d2edfcfeed99124f9e115f992cbef3804682,f6af504f1ba8283fd00af0d6e3c9c1a665d62736,a595235d3cf8f67611efd8395332b64d067b5f1f]:v2.11.5Compare Source
Patch Changes
e1c58611c3c996b4fff98a54e49f00549ff2115d,3e2d1fd315db54a089fedf131cfaa27792bdd049]:v2.11.4Compare Source
Patch Changes
d221ac04c3ee00a3c7a671d9d56e2cfa36943b49,7730c03e128be6754b9e40c086d5cb5c4685ac66,4bda3a498eba36e187dfd9ae673eca12d3f3502c,6adbf7e86927de969aedab665b6a3a8dbf3a6095,2a20dc38dfc40e0b618d5cc826f18a19ddb91aff]:v2.11.3Compare Source
Patch Changes
When a
GraphQLScalarTyperesolver is provided tobuildSubgraphSchema(), omitted configuration options in theGraphQLScalarTypeno longer cause the corresponding properties in the GraphQL document/AST to be cleared. To explicitly clear these properties, usenullfor the configuration option instead. (#3285) (#3285)Updated dependencies [
8c7a2cd655ad3060e9f5c3b106cfbdb59251701c]:v2.11.2Compare Source
Patch Changes
Revert change to @composeDirective definition to specify nullable argument value. (#3283)
We cannot fix the definition as that would break customers using older versions of
subgraph-js. Our validations are already verifying that the values are specified.Updated dependencies [
28c08bef6e691aefc6ed07c0e7057f9cd803b317]:v2.11.1Compare Source
Patch Changes
7799ad1717becf15fb0e82f89619f2ec8a24b4d4,b26794c5724ef23d1f0fd45a40aee3d301557489]:v2.11.0Compare Source
Minor Changes
Patch Changes
1462c91879d41884c0a7e60551d8dd0d67c832d3,9614b26e5a17cbf1f6aaf08f6fcb1c95eb12592d]:v2.10.4Compare Source
Patch Changes
20c75d1d60a48fc289d88c8d29652f1afc7553e4]:v2.10.3Compare Source
Patch Changes
2b88aec38d5bacb6ec815d885fdac47ef415124a,18a9cfaf533602bb37fdf22962539ce0eae948c8,9c0aaa0874c98ae8ce0cc38cad7f6f25d2c29635,f94e7b35c43ed64c67ff25c7aeb86ec0dd73370a]:v2.10.2Compare Source
Patch Changes
v2.10.1Compare Source
Patch Changes
97d81b79c3da10175bdf92c2209039efe352de79]:v2.10.0Compare Source
Patch Changes
When resolving references, skip type resolution if the reference resolves to null. (#3215)
Updated dependencies [
8927e315ab0e865ef3ff12320f265ee95588b899,8927e315ab0e865ef3ff12320f265ee95588b899]:v2.9.5Compare Source
Patch Changes
0d8fca1c8cc375bb8486f11f339984b69267417d]:v2.9.4Compare Source
Patch Changes
22686d640b1e48f6a9aa07e538464db95b536792,22686d640b1e48f6a9aa07e538464db95b536792,22686d640b1e48f6a9aa07e538464db95b536792,22686d640b1e48f6a9aa07e538464db95b536792]:apollographql/router (ghcr.io/apollographql/router)
v2.8.2Compare Source
🐛 Fixes
Support arrays in complex
@keyfields for entity caching (PR #8367)Entity caching now supports arrays (including arrays of objects and scalars) in complex
@keyfields when resolving entities by key. This improves entity matching when using complex@keyfields as primary cache keys.By @aaronArinder, @bnjjj, and @duckki in https://github.com/apollographql/router/pull/8367
Parse scientific notation correctly in Rhai scripts (PR #8528)
The router now correctly parses scientific notation (like
1.5e10) in Rhai scripts and JSON operations. Previously, the Rhai scripting engine failed to parse these numeric formats, causing runtime errors when your scripts processed data containing exponential notation.This fix upgrades Rhai from 1.21.0 to 1.23.6, resolving the parsing issue and ensuring your scripts handle scientific notation seamlessly.
By @BrynCooke in https://github.com/apollographql/router/pull/8528
Support enum types in
@cacheTagdirective format (PR #8496)Composition validation no longer raises an error when using enum types in the
@cacheTagdirective'sformatargument. Previously, only scalar types were accepted.Example:
By @bnjjj in https://github.com/apollographql/router/pull/8496
Improve debugging data with caching flag and enhanced warnings (PR #8459)
Debugging data now includes a flag that indicates to Apollo Sandbox whether the data should be cached, preventing unnecessary local computation. This update also includes improved warnings.
By @bnjjj in https://github.com/apollographql/router/pull/8459
Display cache tags from subgraph responses in debugger (PR #8531)
The debugger now displays cache tags generated from subgraph responses (in
extensions). For performance reasons, these generated cache tags are only displayed when the data has been cached in debug mode.By @bnjjj in https://github.com/apollographql/router/pull/8531
📚 Documentation
Clarify guidance for OpenTelemetry "Recommended" attributes in telemetry documentation
The router telemetry documentation now clarifies that OpenTelemetry's "Recommended" attributes from their development-status GraphQL semantic conventions are experimental and still evolving. Apollo recommends using
requiredattributes instead ofrecommendedattributes because of high cardinality, security, and performance risks with attributes likegraphql.document.Learn more in Router Telemetry.
By @abernix
🧪 Experimental
Prevent panic when record/replay plugin encounters non-UTF-8 header values (PR #8485)
The record/replay plugin no longer panics when externalizing headers with invalid UTF-8 values. Instead, the plugin writes the header keys and errors to a
header_errorsobject for both requests and responses.By @rohan-b99 in https://github.com/apollographql/router/pull/8485
v2.8.1Compare Source
🔒 Security
Fix authorization plugin handling of polymorphic types
Updates the auth plugin to correctly handle access control requirements when processing polymorphic types.
When querying interface types/fields, the auth plugin was verifying only whether all implementations shared the same access control requirements. In cases where interface types/fields did not specify the same access control requirements as the implementations, this could result in unauthorized access to protected data.
The auth plugin was updated to correctly verify that all polymorphic access control requirements are satisfied by the current context.
See GHSA-x33c-7c2v-mrj9 for additional details and the associated CVE number.
By [@dariuszkuc](https://redirect.github.com/dariuszk
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - "after 8am and before 4pm on tuesday" in timezone America/Los_Angeles.
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, 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 Renovate Bot.