-
Notifications
You must be signed in to change notification settings - Fork 117
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
chore(deps): pin dependency @apollo/client to v3.11.10 #519
Open
renovate
wants to merge
1
commit into
master
Choose a base branch
from
renovate/apollo-graphql-packages
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
renovate
bot
changed the title
chore(deps): pin dependency @apollo/client to v3.9.10
chore(deps): pin dependency @apollo/client to v3.9.11
Apr 10, 2024
renovate
bot
force-pushed
the
renovate/apollo-graphql-packages
branch
from
April 10, 2024 13:59
8df16a9
to
4aa8404
Compare
renovate
bot
force-pushed
the
renovate/apollo-graphql-packages
branch
from
April 24, 2024 16:24
4aa8404
to
4575918
Compare
renovate
bot
changed the title
chore(deps): pin dependency @apollo/client to v3.9.11
chore(deps): pin dependency @apollo/client to v3.10.0
Apr 24, 2024
renovate
bot
changed the title
chore(deps): pin dependency @apollo/client to v3.10.0
chore(deps): pin dependency @apollo/client to v3.10.1
Apr 24, 2024
renovate
bot
force-pushed
the
renovate/apollo-graphql-packages
branch
from
April 24, 2024 20:17
4575918
to
3a68ee7
Compare
renovate
bot
force-pushed
the
renovate/apollo-graphql-packages
branch
from
May 3, 2024 18:07
3a68ee7
to
ae9454c
Compare
renovate
bot
changed the title
chore(deps): pin dependency @apollo/client to v3.10.1
chore(deps): pin dependency @apollo/client to v3.10.2
May 3, 2024
renovate
bot
changed the title
chore(deps): pin dependency @apollo/client to v3.10.2
chore(deps): pin dependency @apollo/client to v3.10.3
May 7, 2024
renovate
bot
force-pushed
the
renovate/apollo-graphql-packages
branch
from
May 7, 2024 17:38
ae9454c
to
5d5838f
Compare
renovate
bot
changed the title
chore(deps): pin dependency @apollo/client to v3.10.3
chore(deps): pin dependency @apollo/client to v3.10.4
May 15, 2024
renovate
bot
force-pushed
the
renovate/apollo-graphql-packages
branch
from
May 15, 2024 03:53
5d5838f
to
b8509b3
Compare
renovate
bot
force-pushed
the
renovate/apollo-graphql-packages
branch
from
June 12, 2024 20:19
b8509b3
to
b9c329c
Compare
renovate
bot
changed the title
chore(deps): pin dependency @apollo/client to v3.10.4
chore(deps): pin dependency @apollo/client to v3.10.5
Jun 12, 2024
renovate
bot
force-pushed
the
renovate/apollo-graphql-packages
branch
from
June 21, 2024 14:14
b9c329c
to
e36ef73
Compare
renovate
bot
changed the title
chore(deps): pin dependency @apollo/client to v3.10.5
chore(deps): pin dependency @apollo/client to v3.10.6
Jun 21, 2024
renovate
bot
changed the title
chore(deps): pin dependency @apollo/client to v3.10.6
chore(deps): pin dependency @apollo/client to v3.10.7
Jun 26, 2024
renovate
bot
force-pushed
the
renovate/apollo-graphql-packages
branch
2 times, most recently
from
June 27, 2024 21:20
15edeb5
to
e2e0d59
Compare
renovate
bot
changed the title
chore(deps): pin dependency @apollo/client to v3.10.7
chore(deps): pin dependency @apollo/client to v3.10.8
Jun 27, 2024
renovate
bot
force-pushed
the
renovate/apollo-graphql-packages
branch
from
July 23, 2024 01:39
e2e0d59
to
b456850
Compare
renovate
bot
changed the title
chore(deps): pin dependency @apollo/client to v3.10.8
chore(deps): pin dependency @apollo/client to v3.11.0
Jul 23, 2024
renovate
bot
force-pushed
the
renovate/apollo-graphql-packages
branch
from
July 23, 2024 19:53
b456850
to
5e541ce
Compare
renovate
bot
changed the title
chore(deps): pin dependency @apollo/client to v3.11.0
chore(deps): pin dependency @apollo/client to v3.11.1
Jul 23, 2024
renovate
bot
force-pushed
the
renovate/apollo-graphql-packages
branch
from
July 31, 2024 18:02
5e541ce
to
61a69cd
Compare
renovate
bot
changed the title
chore(deps): pin dependency @apollo/client to v3.11.1
chore(deps): pin dependency @apollo/client to v3.11.2
Jul 31, 2024
renovate
bot
force-pushed
the
renovate/apollo-graphql-packages
branch
from
August 5, 2024 18:23
61a69cd
to
677a736
Compare
renovate
bot
changed the title
chore(deps): pin dependency @apollo/client to v3.11.2
chore(deps): pin dependency @apollo/client to v3.11.3
Aug 5, 2024
renovate
bot
force-pushed
the
renovate/apollo-graphql-packages
branch
from
August 7, 2024 22:25
677a736
to
50eb18a
Compare
renovate
bot
changed the title
chore(deps): pin dependency @apollo/client to v3.11.3
chore(deps): pin dependency @apollo/client to v3.11.4
Aug 7, 2024
renovate
bot
force-pushed
the
renovate/apollo-graphql-packages
branch
from
August 28, 2024 20:13
50eb18a
to
5dd6914
Compare
renovate
bot
changed the title
chore(deps): pin dependency @apollo/client to v3.11.4
chore(deps): pin dependency @apollo/client to v3.11.5
Aug 28, 2024
renovate
bot
force-pushed
the
renovate/apollo-graphql-packages
branch
from
September 3, 2024 18:11
5dd6914
to
0b1ab67
Compare
renovate
bot
changed the title
chore(deps): pin dependency @apollo/client to v3.11.5
chore(deps): pin dependency @apollo/client to v3.11.6
Sep 3, 2024
renovate
bot
force-pushed
the
renovate/apollo-graphql-packages
branch
from
September 4, 2024 19:59
0b1ab67
to
3e76816
Compare
renovate
bot
changed the title
chore(deps): pin dependency @apollo/client to v3.11.6
chore(deps): pin dependency @apollo/client to v3.11.7
Sep 4, 2024
renovate
bot
force-pushed
the
renovate/apollo-graphql-packages
branch
from
September 5, 2024 11:07
3e76816
to
decb570
Compare
renovate
bot
changed the title
chore(deps): pin dependency @apollo/client to v3.11.7
chore(deps): pin dependency @apollo/client to v3.11.8
Sep 5, 2024
renovate
bot
force-pushed
the
renovate/apollo-graphql-packages
branch
from
November 7, 2024 18:23
decb570
to
d0281e7
Compare
renovate
bot
changed the title
chore(deps): pin dependency @apollo/client to v3.11.8
chore(deps): pin dependency @apollo/client to v3.11.9
Nov 7, 2024
renovate
bot
force-pushed
the
renovate/apollo-graphql-packages
branch
from
November 12, 2024 02:10
d0281e7
to
ad1aa19
Compare
renovate
bot
changed the title
chore(deps): pin dependency @apollo/client to v3.11.9
chore(deps): pin dependency @apollo/client to v3.11.10
Nov 12, 2024
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.7.17
->3.11.10
3.9.9
->3.11.10
Add the preset
:preserveSemverRanges
to your config if you don't want to pin your dependencies.Release Notes
apollographql/apollo-client (@apollo/client)
v3.11.10
Compare Source
Patch Changes
1765668
Thanks @mgmolisani! - Fixed a bug when evaluating the devtools flag with the new syntaxdevtools.enabled
that could result totrue
when explicitly set tofalse
.v3.11.9
Compare Source
Patch Changes
a3f95c6
Thanks @jerelmiller! - Fix an issue where errors returned from afetchMore
call from a Suspense hook would cause a Suspense boundary to be shown indefinitely.v3.11.8
Compare Source
Patch Changes
35cf186
Thanks @phryneas! - Fixed a bug where incorrect object access in some Safari extensions could cause a crash.v3.11.7
Compare Source
Patch Changes
e471cef
Thanks @jerelmiller! - Fixes a regression from where passing an invalid identifier tofrom
inuseFragment
would result in the warningTypeError: Cannot read properties of undefined (reading '__typename')
.v3.11.6
Compare Source
Patch Changes
#12049
9c26892
Thanks @phryneas and @maciesielka! - Fix a bug whereuseFragment
did not re-render as expected#12044
04462a2
Thanks @DoctorJohn! - Cache theuseSubscription
hook'srestart
function definition between re-renders.v3.11.5
Compare Source
Patch Changes
#12027
eb3e21b
Thanks @JavaScriptBach! - TypeMutationResult.reset
as an arrow function#12020
82d8cb4
Thanks @jerelmiller! - Better conform to Rules of React by avoiding write of ref in render foruseFragment
.v3.11.4
Compare Source
Patch Changes
#11994
41b17e5
Thanks @jerelmiller! - Update theModifier
function type to allowcache.modify
to return deeply partial data.#11989
e609156
Thanks @phryneas! - Fix a potential crash when callingclearStore
while a query was running.Previously, calling
client.clearStore()
while a query was running had one of these results:useQuery
would stay in aloading: true
state.useLazyQuery
would stay in aloading: true
state, 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 theuseLazyQuery
execute
function will return a result in an error state.#11994
41b17e5
Thanks @jerelmiller! - Prevent accidental distribution oncache.modify
field modifiers when a field is a union type array.v3.11.3
Compare Source
Patch Changes
#11984
5db1659
Thanks @jerelmiller! - Fix an issue where multiple fetches with results that returned errors would sometimes set thedata
property with anerrorPolicy
ofnone
.#11974
c95848e
Thanks @jerelmiller! - Fix an issue wherefetchMore
would write its result data to the cache when using it with ano-cache
fetch policy.#11974
c95848e
Thanks @jerelmiller! - Fix an issue where executingfetchMore
with ano-cache
fetch policy could sometimes result in multiple network requests.#11974
c95848e
Thanks @jerelmiller! -Potentially disruptive change
When calling
fetchMore
with a query that has ano-cache
fetch policy,fetchMore
will now throw if anupdateQuery
function is not provided. This provides a mechanism to merge the results from thefetchMore
call with the query's previous result.v3.11.2
Compare Source
Patch Changes
38c0a2c
Thanks @jerelmiller! - Fix missinggetServerSnapshot
error when usinguseSubscription
on the server.v3.11.1
Compare Source
Patch Changes
#11969
061cab6
Thanks @jerelmiller! - Remove check forwindow.__APOLLO_CLIENT__
when determining whether to connect to Apollo Client Devtools whenconnectToDevtools
ordevtools.enabled
is not specified. This now simply checks to see if the application is in development mode.#11971
ecf77f6
Thanks @jerelmiller! - Prevent thesetTimeout
for suggesting devtools from running in non-browser environments.v3.11.0
Compare Source
Potentially Breaking Fixes
#11789
5793301
Thanks @phryneas! - Changes usages of theGraphQLError
type toGraphQLFormattedError
.This was a type bug - these errors were never
GraphQLError
instancesto begin with, and the
GraphQLError
class 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
FormattedExecutionResult
instead of
ExecutionResult
- the non-"Formatted" versions of these typesare for use on the server only, but don't get transported over the network.
#11626
228429a
Thanks @phryneas! - CallnextFetchPolicy
with "variables-changed" even if there is afetchPolicy
specified.Previously this would only be called when the current
fetchPolicy
was equal to thefetchPolicy
option or the option was not specified. If you usenextFetchPolicy
as a function, expect to see this function called more often.Due to this bug, this also meant that the
fetchPolicy
might be reset to the initialfetchPolicy
, even when you specified anextFetchPolicy
function. If you previously relied on this behavior, you will need to update yournextFetchPolicy
callback 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
d88c7f8
Thanks @jerelmiller! - Add support forsubscribeToMore
function touseQueryRefHandlers
.#11854
3812800
Thanks @jcostello-atlassian! - Support extensions in useSubscription#11923
d88c7f8
Thanks @jerelmiller! - Add support forsubscribeToMore
function touseLoadableQuery
.#11863
98e44f7
Thanks @phryneas! - ReimplementuseSubscription
to fix rules of React violations.#11869
a69327c
Thanks @phryneas! - Rewrite big parts ofuseQuery
anduseLazyQuery
to be more compliant with the Rules of React and React Compiler#11936
1b23337
Thanks @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 theconnectToDevtools
option in favor of a newdevtools
configuration.This option is backwards-compatible with
connectToDevtools
and will be used in the absense of adevtools
option.#11923
d88c7f8
Thanks @jerelmiller! - Add support forsubscribeToMore
function touseBackgroundQuery
.#11930
a768575
Thanks @jerelmiller! - Deprecates experimental schema testing utilities introduced in 3.10 in favor of recommending@apollo/graphql-testing-library
.Patch Changes
#11951
0de03af
Thanks @phryneas! - add React 19 RC topeerDependencies
#11927
2941824
Thanks @phryneas! - Addrestart
function touseSubscription
.#11949
4528918
Thanks @alessbell! - Remove deprecatedwatchFragment
option,canonizeResults
#11937
78332be
Thanks @phryneas! -createSchemaFetch
: simulate serialized errors instead of anApolloError
instance#11902
96422ce
Thanks @phryneas! - Addcause
field toApolloError
.#11806
8df6013
Thanks @phryneas! - MockLink: add query default variables if not specified in mock request#11926
3dd6432
Thanks @phryneas! -watchFragment
: forward additional options todiffOptions
#11946
7d833b8
Thanks @jerelmiller! - Fix issue where mutations were not accessible by Apollo Client Devtools in 3.11.0-rc.0.#11944
8f3d7eb
Thanks @sneyderdev! - AllowIgnoreModifier
to be returned from aoptimisticResponse
function when inferring from aTypedDocumentNode
when used with a generic argument.#11954
4a6e86a
Thanks @phryneas! - Document (and deprecate) the previously undocumentederrors
property on theuseQuery
QueryResult
type.#11719
09a6677
Thanks @phryneas! - Allow wrappingcreateQueryPreloader
#11921
70406bf
Thanks @phryneas! - addignoreResults
option touseSubscription
v3.10.8
Compare Source
Patch Changes
1f0460a
Thanks @jerelmiller! - Allowundefined
to be returned from acache.modify
modifier function when a generic type argument is used.v3.10.7
Compare Source
Patch Changes
#11901
10a8c0a
Thanks @phryneas! - updatecanUseLayoutEffect
check to also allow for layout effects in React Native#11861
1aed0e8
Thanks @henryqdineen! - Defend against non-serializable params ininvariantWrappers
#11905
29755da
Thanks @phryneas! - Add.d.cts
files for cjs bundles#11906
d104759
Thanks @phryneas! - chore: update TypeScript to 5.5v3.10.6
Compare Source
Patch Changes
f745558
Thanks @phryneas! -useMutation
: useuseIsomorphicLayoutEffect
instead ofuseLayoutEffect
v3.10.5
Compare Source
Patch Changes
#11888
7fb7939
Thanks @phryneas! - switchuseRenderGuard
to an approach not accessing React's internals#11511
6536369
Thanks @phryneas! -useLoadableQuery
: ensure thatloadQuery
is updated if the ApolloClient instance changes#11860
8740f19
Thanks @alessbell! - Fixes #11849 by reevaluatingwindow.fetch
each timeBatchHttpLink
uses it, if not configured viaoptions.fetch
. Takes the same approach as PR #8603 which fixed the same issue inHttpLink
.#11852
d502a69
Thanks @phryneas! - Fix a bug where calling theuseMutation
reset
function would point the hook to an outdatedclient
reference.#11329
3d164ea
Thanks @PaLy! - Fix graphQLErrors in Error Link if networkError.result is an empty string#11852
d502a69
Thanks @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
execute
function during render. Please note that this was never supported behavior, and we strongly recommend against it.#11848
ad63924
Thanks @phryneas! - Ensure covariant behavior:MockedResponse<X,Y>
should be assignable toMockedResponse
#11851
45c47be
Thanks @phryneas! - Avoid usage of useRef in useInternalState to prevent ref access in render.#11877
634d91a
Thanks @phryneas! - Add missing name to tuple member (fix TS5084)#11851
45c47be
Thanks @phryneas! - Fix a bug whereuseLazyQuery
would not pick up a client change.v3.10.4
Compare Source
Patch Changes
#11838
8475346
Thanks @alex-kinokon! - Don’t prompt for DevTools installation for browser extension page#11839
6481fe1
Thanks @jerelmiller! - Fix a regression in 3.9.5 where a merge function that returned an incomplete result would not allow the client to refetch in order to fulfill the query.#11844
86984f2
Thanks @jerelmiller! - Honor the@nonreactive
directive when usingcache.watchFragment
or theuseFragment
hook to avoid rerendering when using these directives.#11824
47ad806
Thanks @phryneas! - Create brandedQueryRef
type without exposed properties.This change deprecates
QueryReference
in favor of aQueryRef
type that doesn't expose any properties.This change also updates
preloadQuery
to return a newPreloadedQueryRef
type, which exposes thetoPromise
function as it does today. This means that query refs produced byuseBackgroundQuery
anduseLoadableQuery
now returnQueryRef
types that do not have access to atoPromise
function, which was never meant to be used in combination with these hooks.While we tend to avoid any types of breaking changes in patch releases as this, this change was necessary to support an upcoming version of the React Server Component integration, which needed to omit the
toPromise
function that would otherwise have broken at runtime.Note that this is a TypeScript-only change. At runtime,
toPromise
is still present on all queryRefs currently created by this package - but we strongly want to discourage you from accessing it in all cases except for thePreloadedQueryRef
use case.Migration is as simple as replacing all references to
QueryReference
withQueryRef
, so it should be possible to do this with a search & replace in most code bases:#11845
4c5c820
Thanks @jerelmiller! - Remove@nonreactive
directives from queries passed toMockLink
to ensure they are properly matched.#11837
dff15b1
Thanks @jerelmiller! - Fix an issue where a polled query created in React strict mode may not stop polling after the component unmounts while using thecache-and-network
fetch policy.v3.10.3
Compare Source
Patch Changes
#11811
d67d7f9
Thanks @phryneas! - Adjust some types for React 19 compat#11834
7d8aad4
Thanks @psamim! - Fix error "Cannot convert object to primitive value"v3.10.2
Compare Source
Patch Changes
#11821
2675d3c
Thanks @jerelmiller! - Fix a regression where rerendering a component withuseBackgroundQuery
would recreate thequeryRef
instance when used with React's strict mode.#11821
2675d3c
Thanks @jerelmiller! - Revert the change introduced in3.9.10 via #11738 that disposed of queryRefs synchronously. This change caused too many issues with strict mode.
v3.10.1
Compare Source
Patch Changes
#11792
5876c35
Thanks @phryneas! - AutoCleanedCache: only schedule batched cache cleanup if the cache is full (fixes #11790)#11799
1aca7ed
Thanks @phryneas! -RenderPromises
: usecanonicalStringify
to serializevariables
to ensure query deduplication is properly applied even whenvariables
are specified in a different order.#11803
bf9dd17
Thanks @phryneas! - Update therehackt
dependency to^0.1.0
#11756
60592e9
Thanks @henryqdineen! - Fix operation.setContext() typev3.10.0
Compare Source
Minor Changes
#11605
e2dd4c9
Thanks @alessbell! - AddscreateMockFetch
utility for integration testing that includes the link chain#11760
acd1982
Thanks @alessbell! -createTestSchema
now uses graphql-toolsmergeResolvers
to merge resolvers instead of a shallow merge.#11764
f046aa9
Thanks @alessbell! - RenamecreateProxiedSchema
tocreateTestSchema
andcreateMockFetch
tocreateSchemaFetch
.#11777
5dfc79f
Thanks @alessbell! - CallcreateMockSchema
insidecreateTestSchema
.#11774
2583488
Thanks @alessbell! - Add ability to set min and max delay increateSchemaFetch
#11605
e2dd4c9
Thanks @alessbell! - Adds proxiedSchema and createMockSchema testing utilities#11465
7623da7
Thanks @alessbell! - AddwatchFragment
method to the cache and expose it on ApolloClient, refactoruseFragment
usingwatchFragment
.#11743
78891f9
Thanks @jerelmiller! - Remove alpha designation forqueryRef.toPromise()
to stabilize the API.#11743
78891f9
Thanks @jerelmiller! - Remove alpha designation forcreateQueryPreloader
to stabilize the API.#11783
440563a
Thanks @alessbell! - Moves new testing utilities to their own entrypoint,testing/experimental
Patch Changes
#11757
9825295
Thanks @phryneas! - AdjustuseReadQuery
wrapper logic to work with transported objects.#11771
e72cbba
Thanks @phryneas! - WrapuseQueryRefHandlers
inwrapHook
.#11754
80d2ba5
Thanks @alessbell! - ExportWatchFragmentOptions
andWatchFragmentResult
from main entrypoint and fix bug wherethis
wasn't bound to thewatchFragment
method onApolloClient
.v3.9.11
Compare Source
Patch Changes
04132af
Thanks @jerelmiller! - Fix an issue where usingskipToken
or theskip
option withuseSuspenseQuery
in React's strict mode would perform a network request.v3.9.10
Compare Source
Patch Changes
#11738
b1a5eb8
Thanks @jerelmiller! - Fix an issue where rerenderinguseBackgroundQuery
after thequeryRef
had been disposed, either via the auto dispose timeout or by unmountinguseReadQuery
, would cause thequeryRef
to be recreated potentially resulting in another network request.#11738
b1a5eb8
Thanks @jerelmiller! - Allow queryRefs to be disposed of synchronously when a suspense hook unmounts. This prevents some situations where using a suspense hook with the same query/variables as the disposed queryRef accidentally used the disposed queryRef rather than creating a new instance.#11670
cc5c03b
Thanks @phryneas! - Bail out ofexecuteSubSelectedArray
calls if the array has 0 elements.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 is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about these updates again.
This PR was generated by Mend Renovate. View the repository job log.