chore(deps): update renovate dependency scan #372
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]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
⚠ Artifact update problemRenovate failed to update artifacts related to this branch. You probably do not want to merge this PR as-is. ♻ Renovate will retry this branch, including artifacts, only when one of the following happens:
The artifact failure details are included below: File name: Node/graphql-apollo-globaldynamics/app/pnpm-lock.yamlFile name: Node/graphql-apollo-v1/speakers-rest-api/pnpm-lock.yamlFile name: Node/graphql-apollo-globaldynamics/api/pnpm-lock.yamlFile name: Node/graphql-apollo-globaldynamics/pnpm-lock.yamlFile name: Node/graphql-apollo-v1/pnpm-lock.yamlFile name: TypeScript/ts4_3/pnpm-lock.yamlFile name: Node/graphql-express/pnpm-lock.yaml |
renovate
bot
force-pushed
the
renovate/all
branch
10 times, most recently
from
50e8e40
to
a5ac153
Compare
renovate
bot
force-pushed
the
renovate/all
branch
10 times, most recently
from
b729482
to
f282da7
Compare
renovate
bot
force-pushed
the
renovate/all
branch
6 times, most recently
from
098fc54
to
97aa442
Compare
renovate
bot
force-pushed
the
renovate/all
branch
3 times, most recently
from
f1d4d99
to
b883c9f
Compare
renovate
bot
force-pushed
the
renovate/all
branch
7 times, most recently
from
06a7f1f
to
2a08c1c
Compare
renovate
bot
force-pushed
the
renovate/all
branch
11 times, most recently
from
8c29108
to
3a383a8
Compare
renovate
bot
force-pushed
the
renovate/all
branch
10 times, most recently
from
fb9699d
to
e6a2601
Compare
renovate
bot
force-pushed
the
renovate/all
branch
from
e6a2601
to
5d91dd7
Compare
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.9.4->3.10.47.23.9->7.24.71.7.0->1.9.0^0.41.0->^0.47.01.21.0->1.25.025.0.7->25.0.86.4.2->6.4.514.2.1->14.3.114.5.1->14.5.220.11.17->20.14.21.6.7->1.7.21.19.0->1.20.21.4.5->1.4.64.3.4->4.3.516.3.1->16.4.510.8.0->10.12.26.5.1->6.5.22.4.5->2.4.69.0.1->9.0.119.0.0->9.0.215.2.2->15.2.5^7.0.0->^6.0.010.3.0->10.4.06.3.0->6.7.08.1.2->8.4.120.11.0->20.14.03.0.3->3.1.33.0.3->3.1.33.0.1->3.1.33.0.1->3.1.3^0.29.0->^0.30.01.9.0->1.9.43.2.5->3.3.13.0.3->3.3.118.2.0->18.3.118.2.0->18.3.16.22.0->6.23.14.10.0->4.18.07.1.6->7.2.26.37.0->6.37.34.2.10->4.2.185.0.4->5.4.55.3.3->5.4.55.3.3->5.4.59.0.0->9.0.113.11.0->13.12.0Release Notes
apollographql/apollo-client (@apollo/client)
v3.10.4Compare Source
Patch Changes
#11838
8475346Thanks @alex-kinokon! - Don’t prompt for DevTools installation for browser extension page#11839
6481fe1Thanks @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
86984f2Thanks @jerelmiller! - Honor the@nonreactivedirective when usingcache.watchFragmentor theuseFragmenthook to avoid rerendering when using these directives.#11824
47ad806Thanks @phryneas! - Create brandedQueryReftype without exposed properties.This change deprecates
QueryReferencein favor of aQueryReftype that doesn't expose any properties.This change also updates
preloadQueryto return a newPreloadedQueryReftype, which exposes thetoPromisefunction as it does today. This means that query refs produced byuseBackgroundQueryanduseLoadableQuerynow returnQueryReftypes that do not have access to atoPromisefunction, 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
toPromisefunction that would otherwise have broken at runtime.Note that this is a TypeScript-only change. At runtime,
toPromiseis 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 thePreloadedQueryRefuse case.Migration is as simple as replacing all references to
QueryReferencewithQueryRef, so it should be possible to do this with a search & replace in most code bases:#11845
4c5c820Thanks @jerelmiller! - Remove@nonreactivedirectives from queries passed toMockLinkto ensure they are properly matched.#11837
dff15b1Thanks @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-networkfetch policy.v3.10.3Compare Source
Patch Changes
#11811
d67d7f9Thanks @phryneas! - Adjust some types for React 19 compat#11834
7d8aad4Thanks @psamim! - Fix error "Cannot convert object to primitive value"v3.10.2Compare Source
Patch Changes
#11821
2675d3cThanks @jerelmiller! - Fix a regression where rerendering a component withuseBackgroundQuerywould recreate thequeryRefinstance when used with React's strict mode.#11821
2675d3cThanks @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.1Compare Source
Patch Changes
#11792
5876c35Thanks @phryneas! - AutoCleanedCache: only schedule batched cache cleanup if the cache is full (fixes #11790)#11799
1aca7edThanks @phryneas! -RenderPromises: usecanonicalStringifyto serializevariablesto ensure query deduplication is properly applied even whenvariablesare specified in a different order.#11803
bf9dd17Thanks @phryneas! - Update therehacktdependency to^0.1.0#11756
60592e9Thanks @henryqdineen! - Fix operation.setContext() typev3.10.0Compare Source
Minor Changes
#11605
e2dd4c9Thanks @alessbell! - AddscreateMockFetchutility for integration testing that includes the link chain#11760
acd1982Thanks @alessbell! -createTestSchemanow uses graphql-toolsmergeResolversto merge resolvers instead of a shallow merge.#11764
f046aa9Thanks @alessbell! - RenamecreateProxiedSchematocreateTestSchemaandcreateMockFetchtocreateSchemaFetch.#11777
5dfc79fThanks @alessbell! - CallcreateMockSchemainsidecreateTestSchema.#11774
2583488Thanks @alessbell! - Add ability to set min and max delay increateSchemaFetch#11605
e2dd4c9Thanks @alessbell! - Adds proxiedSchema and createMockSchema testing utilities#11465
7623da7Thanks @alessbell! - AddwatchFragmentmethod to the cache and expose it on ApolloClient, refactoruseFragmentusingwatchFragment.#11743
78891f9Thanks @jerelmiller! - Remove alpha designation forqueryRef.toPromise()to stabilize the API.#11743
78891f9Thanks @jerelmiller! - Remove alpha designation forcreateQueryPreloaderto stabilize the API.#11783
440563aThanks @alessbell! - Moves new testing utilities to their own entrypoint,testing/experimentalPatch Changes
#11757
9825295Thanks @phryneas! - AdjustuseReadQuerywrapper logic to work with transported objects.#11771
e72cbbaThanks @phryneas! - WrapuseQueryRefHandlersinwrapHook.#11754
80d2ba5Thanks @alessbell! - ExportWatchFragmentOptionsandWatchFragmentResultfrom main entrypoint and fix bug wherethiswasn't bound to thewatchFragmentmethod onApolloClient.v3.9.11Compare Source
Patch Changes
04132afThanks @jerelmiller! - Fix an issue where usingskipTokenor theskipoption withuseSuspenseQueryin React's strict mode would perform a network request.v3.9.10Compare Source
Patch Changes
#11738
b1a5eb8Thanks @jerelmiller! - Fix an issue where rerenderinguseBackgroundQueryafter thequeryRefhad been disposed, either via the auto dispose timeout or by unmountinguseReadQuery, would cause thequeryRefto be recreated potentially resulting in another network request.#11738
b1a5eb8Thanks @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
cc5c03bThanks @phryneas! - Bail out ofexecuteSubSelectedArraycalls if the array has 0 elements.v3.9.9Compare Source
Patch Changes
466ef82Thanks @PiR1! - Immediately dispose of thequeryRefifuseBackgroundQueryunmounts before the auto dispose timeout kicks in.v3.9.8Compare Source
Patch Changes
#11706
8619bc7Thanks @jerelmiller! - Fix issue in all suspense hooks where returning an empty array after callingfetchMorewould rerender the component with an empty list.#11694
835d5f3Thanks @phryneas! - ExposesetErrorMessageHandlerfrom@apollo/client/deventrypoint.#11689
cb8ffe5Thanks @jerelmiller! - Fix issue where passing a newfromoption touseFragmentwould first render with the previous value before rerendering with the correct value.#11713
642092cThanks @jerelmiller! - Fix issue where setting a defaultwatchQueryoption in theApolloClientconstructor could breakstartTransitionwhen used with suspense hooks.v3.9.7Compare Source
Patch Changes
#11659
652a61eThanks @phryneas! - MakeuseRenderGuardmore resilient to changes in React internals.#11594
50b1097Thanks @alessbell! - Adds a fix for multipart subscriptions that terminate with payload: nullv3.9.6Compare Source
Patch Changes
#11617
f1d8bc4Thanks @phryneas! - Allow Apollo Client instance to intercept hook functionality#11638
bf93adaThanks @jerelmiller! - Fix issue where callingfetchMorefrom a suspense-enabled hook insidestartTransitioncaused an unnecessary rerender.v3.9.5Compare Source
Patch Changes
#11595
8c20955Thanks @phryneas! - Bumps the dependencyrehacktto 0.0.5#11592
1133469Thanks @Stephen2! - StrengthenMockedResponse.newDatatype#11579
1ba2fd9Thanks @jerelmiller! - Fix issue where partial data is reported touseQuerywhen usingnotifyOnNetworkStatusChangeafter it errors while another overlapping query succeeds.#11579
1ba2fd9Thanks @jerelmiller! - Fix an issue where a partial cache write for an errored query would result in automatically refetching that query.#11562
65ab695Thanks @mspiess! - Mocks with an infinite delay no longer require result or errorbabel/babel (@babel/preset-env)
v7.24.7Compare Source
🐛 Bug Fix
babel-nodebabel-traverseconstantViolationswith destructuring (@liuxingbaoyu)babel-helper-transform-fixture-test-runner,babel-plugin-proposal-explicit-resource-managementusinginswitchcorrectly (@liuxingbaoyu)🏠 Internal
babel-helpers,babel-runtime-corejs2,babel-runtime-corejs3,babel-runtimev7.24.6Compare Source
🐛 Bug Fix
babel-helper-create-class-features-plugin,babel-plugin-transform-class-propertiesbabel-core,babel-generator,babel-plugin-transform-modules-commonjsbabel-helper-create-class-features-plugin,babel-plugin-proposal-decorators