- 
          
 - 
                Notifications
    
You must be signed in to change notification settings  - Fork 8.6k
 
fix(deps): update dependency @apollo/client to v3.11.8 - abandoned #14132
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
Conversation
4045936    to
    2598e8c      
    Compare
  
    ee9f950    to
    ceef536      
    Compare
  
    ceef536    to
    3f49a42      
    Compare
  
    3f49a42    to
    4f5440d      
    Compare
  
    4f5440d    to
    bec24ac      
    Compare
  
    bec24ac    to
    63df3f9      
    Compare
  
    c06d147    to
    82e0e73      
    Compare
  
    82e0e73    to
    90a5eb8      
    Compare
  
    90a5eb8    to
    1cef083      
    Compare
  
    1cef083    to
    bc9ec37      
    Compare
  
    bc9ec37    to
    d427076      
    Compare
  
    d427076    to
    8bed970      
    Compare
  
    8bed970    to
    6fcb448      
    Compare
  
    
          CI Failure Feedback 🧐(Checks updated until commit 6fcb448)
  | 
    
Signed-off-by: Viet Nguyen Duc <[email protected]>
          Edited/Blocked NotificationRenovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR. You can manually request rebase by checking the rebase/retry box above.  | 
    
          Autoclosing SkippedThis PR has been flagged for autoclosing. However, it is being skipped due to the branch being already modified. Please close/delete it manually or report a bug if you think this is in error.  | 
    
| 
           Resolved with commit 215e20b !  | 
    
This PR contains the following updates:
3.10.4->3.11.8Release Notes
apollographql/apollo-client (@apollo/client)
v3.11.8Compare Source
Patch Changes
35cf186Thanks @phryneas! - Fixed a bug where incorrect object access in some Safari extensions could cause a crash.v3.11.7Compare Source
Patch Changes
e471cefThanks @jerelmiller! - Fixes a regression from where passing an invalid identifier tofrominuseFragmentwould result in the warningTypeError: Cannot read properties of undefined (reading '__typename').v3.11.6Compare Source
Patch Changes
#12049
9c26892Thanks @phryneas and @maciesielka! - Fix a bug whereuseFragmentdid not re-render as expected#12044
04462a2Thanks @DoctorJohn! - Cache theuseSubscriptionhook'srestartfunction definition between re-renders.v3.11.5Compare Source
Patch Changes
#12027
eb3e21bThanks @JavaScriptBach! - TypeMutationResult.resetas an arrow function#12020
82d8cb4Thanks @jerelmiller! - Better conform to Rules of React by avoiding write of ref in render foruseFragment.v3.11.4Compare Source
Patch Changes
#11994
41b17e5Thanks @jerelmiller! - Update theModifierfunction type to allowcache.modifyto return deeply partial data.#11989
e609156Thanks @phryneas! - Fix a potential crash when callingclearStorewhile a query was running.Previously, calling
client.clearStore()while a query was running had one of these results:useQuerywould stay in aloading: truestate.useLazyQuerywould stay in aloading: truestate, but also crash with a"Cannot read property 'data' of undefined"error.Now, in both cases, the hook will enter an error state with a
networkError, and the promise returned by theuseLazyQueryexecutefunction will return a result in an error state.#11994
41b17e5Thanks @jerelmiller! - Prevent accidental distribution oncache.modifyfield modifiers when a field is a union type array.v3.11.3Compare Source
Patch Changes
#11984
5db1659Thanks @jerelmiller! - Fix an issue where multiple fetches with results that returned errors would sometimes set thedataproperty with anerrorPolicyofnone.#11974
c95848eThanks @jerelmiller! - Fix an issue wherefetchMorewould write its result data to the cache when using it with ano-cachefetch policy.#11974
c95848eThanks @jerelmiller! - Fix an issue where executingfetchMorewith ano-cachefetch policy could sometimes result in multiple network requests.#11974
c95848eThanks @jerelmiller! -Potentially disruptive change
When calling
fetchMorewith a query that has ano-cachefetch policy,fetchMorewill now throw if anupdateQueryfunction is not provided. This provides a mechanism to merge the results from thefetchMorecall with the query's previous result.v3.11.2Compare Source
Patch Changes
38c0a2cThanks @jerelmiller! - Fix missinggetServerSnapshoterror when usinguseSubscriptionon the server.v3.11.1Compare Source
Patch Changes
#11969
061cab6Thanks @jerelmiller! - Remove check forwindow.__APOLLO_CLIENT__when determining whether to connect to Apollo Client Devtools whenconnectToDevtoolsordevtools.enabledis not specified. This now simply checks to see if the application is in development mode.#11971
ecf77f6Thanks @jerelmiller! - Prevent thesetTimeoutfor suggesting devtools from running in non-browser environments.v3.11.0Compare Source
Potentially Breaking Fixes
#11789
5793301Thanks @phryneas! - Changes usages of theGraphQLErrortype toGraphQLFormattedError.This was a type bug - these errors were never
GraphQLErrorinstancesto begin with, and the
GraphQLErrorclass has additional properties that cannever be correctly rehydrated from a GraphQL result.
The correct type to use here is
GraphQLFormattedError.Similarly, please ensure to use the type
FormattedExecutionResultinstead of
ExecutionResult- the non-"Formatted" versions of these typesare for use on the server only, but don't get transported over the network.
#11626
228429aThanks @phryneas! - CallnextFetchPolicywith "variables-changed" even if there is afetchPolicyspecified.Previously this would only be called when the current
fetchPolicywas equal to thefetchPolicyoption or the option was not specified. If you usenextFetchPolicyas a function, expect to see this function called more often.Due to this bug, this also meant that the
fetchPolicymight be reset to the initialfetchPolicy, even when you specified anextFetchPolicyfunction. If you previously relied on this behavior, you will need to update yournextFetchPolicycallback function to implement this resetting behavior.As an example, if your code looked like the following:
Update your function to the following to reimplement the resetting behavior:
Minor Changes
#11923
d88c7f8Thanks @jerelmiller! - Add support forsubscribeToMorefunction touseQueryRefHandlers.#11854
3812800Thanks @jcostello-atlassian! - Support extensions in useSubscription#11923
d88c7f8Thanks @jerelmiller! - Add support forsubscribeToMorefunction touseLoadableQuery.#11863
98e44f7Thanks @phryneas! - ReimplementuseSubscriptionto fix rules of React violations.#11869
a69327cThanks @phryneas! - Rewrite big parts ofuseQueryanduseLazyQueryto be more compliant with the Rules of React and React Compiler#11936
1b23337Thanks @jerelmiller! - Add the ability to specify a name for the client instance for use with Apollo Client Devtools. This is useful when instantiating multiple clients to identify the client instance more easily. This deprecates theconnectToDevtoolsoption in favor of a newdevtoolsconfiguration.This option is backwards-compatible with
connectToDevtoolsand will be used in the absense of adevtoolsoption.#11923
d88c7f8Thanks @jerelmiller! - Add support forsubscribeToMorefunction touseBackgroundQuery.#11930
a768575Thanks @jerelmiller! - Deprecates experimental schema testing utilities introduced in 3.10 in favor of recommending@apollo/graphql-testing-library.Patch Changes
#11951
0de03afThanks @phryneas! - add React 19 RC topeerDependencies#11927
2941824Thanks @phryneas! - Addrestartfunction touseSubscription.#11949
4528918Thanks @alessbell! - Remove deprecatedwatchFragmentoption,canonizeResults#11937
78332beThanks @phryneas! -createSchemaFetch: simulate serialized errors instead of anApolloErrorinstance#11902
96422ceThanks @phryneas! - Addcausefield toApolloError.#11806
8df6013Thanks @phryneas! - MockLink: add query default variables if not specified in mock request#11926
3dd6432Thanks @phryneas! -watchFragment: forward additional options todiffOptions#11946
7d833b8Thanks @jerelmiller! - Fix issue where mutations were not accessible by Apollo Client Devtools in 3.11.0-rc.0.#11944
8f3d7ebThanks @sneyderdev! - AllowIgnoreModifierto be returned from aoptimisticResponsefunction when inferring from aTypedDocumentNodewhen used with a generic argument.#11954
4a6e86aThanks @phryneas! - Document (and deprecate) the previously undocumentederrorsproperty on theuseQueryQueryResulttype.#11719
09a6677Thanks @phryneas! - Allow wrappingcreateQueryPreloader#11921
70406bfThanks @phryneas! - addignoreResultsoption touseSubscriptionv3.10.8Compare Source
Patch Changes
1f0460aThanks @jerelmiller! - Allowundefinedto be returned from acache.modifymodifier function when a generic type argument is used.v3.10.7Compare Source
Patch Changes
#11901
10a8c0aThanks @phryneas! - updatecanUseLayoutEffectcheck to also allow for layout effects in React Native#11861
1aed0e8Thanks @henryqdineen! - Defend against non-serializable params ininvariantWrappers#11905
29755daThanks @phryneas! - Add.d.ctsfiles for cjs bundles#11906
d104759Thanks @phryneas! - chore: update TypeScript to 5.5v3.10.6Compare Source
Patch Changes
f745558Thanks @phryneas! -useMutation: useuseIsomorphicLayoutEffectinstead ofuseLayoutEffectv3.10.5Compare Source
Patch Changes
#11888
7fb7939Thanks @phryneas! - switchuseRenderGuardto an approach not accessing React's internals#11511
6536369Thanks @phryneas! -useLoadableQuery: ensure thatloadQueryis updated if the ApolloClient instance changes#11860
8740f19Thanks @alessbell! - Fixes #11849 by reevaluatingwindow.fetcheach timeBatchHttpLinkuses it, if not configured viaoptions.fetch. Takes the same approach as PR #8603 which fixed the same issue inHttpLink.#11852
d502a69Thanks @phryneas! - Fix a bug where calling theuseMutationresetfunction would point the hook to an outdatedclientreference.#11329
3d164eaThanks @PaLy! - Fix graphQLErrors in Error Link if networkError.result is an empty string#11852
d502a69Thanks @phryneas! - Prevent writing to a ref in render inuseMutation.As a result, you might encounter problems in the future if you call the mutation's
executefunction during render. Please note that this was never supported behavior, and we strongly recommend against it.#11848
ad63924Thanks @phryneas! - Ensure covariant behavior:MockedResponse<X,Y>should be assignable toMockedResponse#11851
45c47beThanks @phryneas! - Avoid usage of useRef in useInternalState to prevent ref access in render.#11877
634d91aThanks @phryneas! - Add missing name to tuple member (fix TS5084)#11851
45c47beThanks @phryneas! - Fix a bug whereuseLazyQuerywould not pick up a client change.Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), 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.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.