Skip to content
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

fix: update dependency @apollo/client to v3.10.4 (release-bot/next-v15.x) #2120

Open
wants to merge 1 commit into
base: release-bot/next-v15.x
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Feb 24, 2022

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@apollo/client (source) 3.4.17 -> 3.10.4 age adoption passing confidence

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.


Release Notes

apollographql/apollo-client (@​apollo/client)

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 using cache.watchFragment or the useFragment hook to avoid rerendering when using these directives.

  • #​11824 47ad806 Thanks @​phryneas! - Create branded QueryRef type without exposed properties.

    This change deprecates QueryReference in favor of a QueryRef type that doesn't expose any properties.
    This change also updates preloadQuery to return a new PreloadedQueryRef type, which exposes the toPromise function as it does today. This means that query refs produced by useBackgroundQuery and useLoadableQuery now return QueryRef types that do not have access to a toPromise 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 the PreloadedQueryRef use case.

    Migration is as simple as replacing all references to QueryReference with QueryRef, so it should be possible to do this with a search & replace in most code bases:

    -import { QueryReference } from '@​apollo/client'
    +import { QueryRef } from '@​apollo/client'
    
    - function Component({ queryRef }: { queryRef: QueryReference<TData> }) {
    + function Component({ queryRef }: { queryRef: QueryRef<TData> }) {
      // ...
    }
  • #​11845 4c5c820 Thanks @​jerelmiller! - Remove @nonreactive directives from queries passed to MockLink 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 the cache-and-network fetch policy.

v3.10.3

Compare Source

Patch Changes

v3.10.2

Compare Source

Patch Changes

v3.10.1

Compare Source

Patch Changes

v3.10.0

Compare Source

Minor Changes
Patch Changes

v3.9.11

Compare Source

Patch Changes
  • #​11769 04132af Thanks @​jerelmiller! - Fix an issue where using skipToken or the skip option with useSuspenseQuery 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 rerendering useBackgroundQuery after the queryRef had been disposed, either via the auto dispose timeout or by unmounting useReadQuery, would cause the queryRef 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 of executeSubSelectedArray calls if the array has 0 elements.

v3.9.9

Compare Source

Patch Changes
  • #​11696 466ef82 Thanks @​PiR1! - Immediately dispose of the queryRef if useBackgroundQuery unmounts before the auto dispose timeout kicks in.

v3.9.8

Compare Source

Patch Changes
  • #​11706 8619bc7 Thanks @​jerelmiller! - Fix issue in all suspense hooks where returning an empty array after calling fetchMore would rerender the component with an empty list.

  • #​11694 835d5f3 Thanks @​phryneas! - Expose setErrorMessageHandler from @apollo/client/dev entrypoint.

  • #​11689 cb8ffe5 Thanks @​jerelmiller! - Fix issue where passing a new from option to useFragment would first render with the previous value before rerendering with the correct value.

  • #​11713 642092c Thanks @​jerelmiller! - Fix issue where setting a default watchQuery option in the ApolloClient constructor could break startTransition when used with suspense hooks.

v3.9.7

Compare Source

Patch Changes

v3.9.6

Compare Source

Patch Changes

v3.9.5

Compare Source

Patch Changes

v3.9.4

Compare Source

Patch Changes

v3.9.3

Compare Source

Patch Changes

v3.9.2

Compare Source

Patch Changes

v3.9.1

Compare Source

Patch Changes

v3.9.0

Compare Source

Minor Changes
Memory optimizations
  • #​11424 62f3b6d Thanks @​phryneas! - Simplify RetryLink, fix potential memory leak

    Historically, RetryLink would keep a values array of all previous values, in case the operation would get an additional subscriber at a later point in time.

    In practice, this could lead to a memory leak (#​11393) and did not serve any further purpose, as the resulting observable would only be subscribed to by Apollo Client itself, and only once - it would be wrapped in a Concast before being exposed to the user, and that Concast would handle subscribers on its own.

  • #​11435 5cce53e Thanks @​phryneas! - Deprecates canonizeResults.

    Using canonizeResults can result in memory leaks so we generally do not recommend using this option anymore. A future version of Apollo Client will contain a similar feature without the risk of memory leaks.

  • #​11254 d08970d Thanks @​benjamn! - Decouple canonicalStringify from ObjectCanon for better time and memory performance.

  • #​11356 cc4ac7e Thanks @​phryneas! - Fix a potential memory leak in FragmentRegistry.transform and FragmentRegistry.findFragmentSpreads that would hold on to passed-in DocumentNodes for too long.

  • #​11370 25e2cb4 Thanks @​phryneas! - parse function: improve memory management

    • use LRU WeakCache instead of Map to keep a limited number of parsed results
    • cache is initiated lazily, only when needed
    • expose parse.resetCache() method
  • #​11389 139acd1 Thanks @​phryneas! - documentTransform: use optimism and WeakCache instead of directly storing data on the Trie

  • #​11358 7d939f8 Thanks @​phryneas! - Fixes a potential memory leak in Concast that might have been triggered when Concast was used outside of Apollo Client.

  • #​11344 bd26676 Thanks @​phryneas! - Add a resetCache method to DocumentTransform and hook InMemoryCache.addTypenameTransform up to InMemoryCache.gc

  • #​11367 30d17bf Thanks @​phryneas! - print: use WeakCache instead of WeakMap

  • #​11387 4dce867 Thanks @​phryneas! - QueryManager.transformCache: use WeakCache instead of WeakMap

  • #​11369 2a47164 Thanks @​phryneas! - Persisted Query Link: improve memory management

    • use LRU WeakCache instead of WeakMap to keep a limited number of hash results
    • hash cache is initiated lazily, only when needed
    • expose persistedLink.resetHashCache() method
    • reset hash cache if the upstream server reports it doesn't accept persisted queries
  • #​10804 221dd99 Thanks @​phryneas! - use WeakMap in React Native with Hermes

  • #​11355 7d8e184 Thanks @​phryneas! - InMemoryCache.gc now also triggers FragmentRegistry.resetCaches (if there is a FragmentRegistry)

  • #​11409 2e7203b Thanks @​phryneas! - Adds an experimental ApolloClient.getMemoryInternals helper

  • #​11343 776631d Thanks @​phryneas! - Add reset method to print, hook up to InMemoryCache.gc

Suspense-enabled data fetching on user interaction with useLoadableQuery
  • #​11300 a815873 Thanks @​jerelmiller! - Introduces a new useLoadableQuery hook. This hook works similarly to useBackgroundQuery in that it returns a queryRef that can be used to suspend a component via the useReadQuery hook. It provides a more ergonomic way to load the query during a user interaction (for example when wanting to preload some data) that would otherwise be clunky with useBackgroundQuery.

    function App() {
      const [loadQuery, queryRef, { refetch, fetchMore, reset }] =
        useLoadableQuery(query, options);
    
      return (
        <>
          <button onClick={() => loadQuery(variables)}>Load query</button>
          <Suspense fallback={<SuspenseFallback />}>
            {queryRef && <Child queryRef={queryRef} />}
          </Suspense>
        </>
      );
    }
    
    function Child({ queryRef }) {
      const { data } = useReadQuery(queryRef);
    
      // ...
    }
Begin preloading outside of React with createQueryPreloader
  • #​11412 58db5c3 Thanks @​jerelmiller! - Add the ability to start preloading a query outside React to begin fetching as early as possible. Call createQueryPreloader to create a preloadQuery function which can be called to start fetching a query. This returns a queryRef which is passed to useReadQuery and suspended until the query is done fetching.
Testing utility improvements
  • #​11178 4d64a6f Thanks @​sebakerckhof! - Support re-using of mocks in the MockedProvider

  • #​6701 8d2b4e1 Thanks @​prowe! - Ability to dynamically match mocks

    Adds support for a new property MockedResponse.variableMatcher: a predicate function that accepts a variables param. If true, the variables will be passed into the ResultFunction to help dynamically build a response.

New useQueryRefHandlers hook
  • #​11412 58db5c3 Thanks @​jerelmiller! - Create a new useQueryRefHandlers hook that returns refetch and fetchMore functions for a given queryRef. This is useful to get access to handlers for a queryRef that was created by createQueryPreloader or when the handlers for a queryRef produced by a different component are inaccessible.

    const MyComponent({ queryRef }) {
      const { refetch, fetchMore } = useQueryRefHandlers(queryRef);
    
      // ...
    }
Bail out of optimisticResponse updates with the IGNORE sentinel object
  • #​11410 07fcf6a Thanks @​sf-twingate! - Allow returning IGNORE sentinel object from optimisticResponse functions to bail-out from the optimistic update.

    Consider this example:

    const UPDATE_COMMENT = gql`
      mutation UpdateComment($commentId: ID!, $commentContent: String!) {
        updateComment(commentId: $commentId, content: $commentContent) {
          id
          __typename
          content
        }
      }
    `;
    
    function CommentPageWithData() {
      const [mutate] = useMutation(UPDATE_COMMENT);
      return (
        <Comment
          updateComment={({ commentId, commentContent }) =>
            mutate({
              variables: { commentId, commentContent },
              optimisticResponse: (vars, { IGNORE }) => {
                if (commentContent === "foo") {
                  // conditionally bail out of optimistic updates
                  return IGNORE;
                }
                return {
                  updateComment: {
                    id: commentId,
                    __typename: "Comment",
                    content: commentContent,
                  },
                };
              },
            })
          }
        />
      );
    }

    The IGNORE sentinel can be destructured from the second parameter in the callback function signature passed to optimisticResponse.

    const preloadQuery = createQueryPreloader(client);
    const queryRef = preloadQuery(QUERY, { variables, ...otherOptions });
    
    function App() {
      return {
        <Suspense fallback={<div>Loading</div>}>
          <MyQuery />
        </Suspense>
      }
    }
    
    function MyQuery() {
      const { data } = useReadQuery(queryRef);
    
      // do something with data
    }
Network adapters for multipart subscriptions usage with Relay and urql
  • #​11301 46ab032 Thanks @​alessbell! - Add multipart subscription network adapters for Relay and urql

    Relay
    import { createFetchMultipartSubscription } from "@&#8203;apollo/client/utilities/subscriptions/relay";
    import { Environment, Network, RecordSource, Store } from "relay-runtime";
    
    const fetchMultipartSubs = createFetchMultipartSubscription(
      "http://localhost:4000",
    );
    
    const network = Network.create(fetchQuery, fetchMultipartSubs);
    
    export const RelayEnvironment = new Environment({
      network,
      store: new Store(new RecordSource()),
    });
    Urql
    import { createFetchMultipartSubscription } from "@&#8203;apollo/client/utilities/subscriptions/urql";
    import { Client, fetchExchange, subscriptionExchange } from "@&#8203;urql/core";
    
    const url = "http://localhost:4000";
    
    const multipartSubscriptionForwarder = createFetchMultipartSubscription(url);
    
    const client = new Client({
      url,
      exchanges: [
        fetchExchange,
        subscriptionExchange({
          forwardSubscription: multipartSubscriptionForwarder,
        }),
      ],
    });
skipPollAttempt callback function
  • #​11397 3f7eecb Thanks @​aditya-kumawat! - Adds a new skipPollAttempt callback function that's called whenever a refetch attempt occurs while polling. If the function returns true, the refetch is skipped and not reattempted until the next poll interval. This will solve the frequent use-case of disabling polling when the window is inactive.

    useQuery(QUERY, {
      pollInterval: 1000,
      skipPollAttempt: () => document.hidden, // or !document.hasFocus()
    });
    // or define it globally
    new ApolloClient({
      defaultOptions: {
        watchQuery: {
          skipPollAttempt: () => document.hidden, // or !document.hasFocus()
        },
      },
    });
QueryManager.inFlightLinkObservables now uses a strong Trie as an internal data structure
  • #​11345 1759066 Thanks @​phryneas!

    Warning: requires @apollo/experimental-nextjs-app-support update

    If you are using @apollo/experimental-nextjs-app-support, you will need to update that to at least 0.5.2, as it accesses this internal data structure.

More Minor Changes

  • #​11202 7c2bc08 Thanks @​benjamn! - Prevent QueryInfo#markResult mutation of result.data and return cache data consistently whether complete or incomplete.

  • #​11442 4b6f2bc Thanks @​jerelmiller! - Remove the need to call retain from useLoadableQuery since useReadQuery will now retain the query. This means that a queryRef that is not consumed by useReadQuery within the given autoDisposeTimeoutMs will now be auto diposed for you.

    Thanks to #​11412, disposed query refs will be automatically resubscribed to the query when consumed by useReadQuery after it has been disposed.

  • #​11438 6d46ab9 Thanks @​jerelmiller! - Remove the need to call retain from useBackgroundQuery since useReadQuery will now retain the query. This means that a queryRef that is not consumed by useReadQuery within the given autoDisposeTimeoutMs will now be auto diposed for you.

    Thanks to #​11412, disposed query refs will be automatically resubscribed to the query when consumed by useReadQuery after it has been disposed.

  • #​11175 d6d1491 Thanks @​phryneas! - To work around issues in React Server Components, especially with bundling for
    the Next.js "edge" runtime we now use an external package to wrap react imports
    instead of importing React directly.

  • #​11495 1190aa5 Thanks @​jerelmiller! - Increase the default memory limits for executeSelectionSet and executeSelectionSetArray.

Patch Changes

  • #​11275 3862f9b Thanks @​phryneas! - Add a defaultContext option and property on ApolloClient, e.g. for keeping track of changing auth tokens or dependency injection.

    This can be used e.g. in authentication scenarios, where a new token might be generated outside of the link chain and should passed into the link chain.

    import { ApolloClient, createHttpLink, InMemoryCache } from "@&#8203;apollo/client";
    import { setContext } from "@&#8203;apollo/client/link/context";
    
    const httpLink = createHttpLink({
      uri: "/graphql",
    });
    
    const authLink = setContext((_, { headers, token }) => {
      return {
        headers: {
          ...headers,
          authorization: token ? `Bearer ${token}` : "",
        },
      };
    });
    
    const client = new ApolloClient({
      link: authLink.concat(httpLink),
      cache: new InMemoryCache(),
    });
    
    // somewhere else in your application
    function onNewToken(newToken) {
      // token can now be changed for future requests without need for a global
      // variable, scoped ref or recreating the client
      client.defaultContext.token = newToken;
    }
  • #​11443 ff5a332 Thanks @​phryneas! - Adds a deprecation warning to the HOC and render prop APIs.

    The HOC and render prop APIs have already been deprecated since 2020,
    but we previously didn't have a @deprecated tag in the DocBlocks.

  • #​11385 d9ca4f0 Thanks @​phryneas! - ensure defaultContext is also used for mutations and subscriptions

  • #​11503 67f62e3 Thanks @​jerelmiller! - Release changes from v3.8.10

  • #​11078 14edebe Thanks @​phryneas! - ObservableQuery: prevent reporting results of previous queries if the variables changed since

  • #​11439 33454f0 Thanks @​jerelmiller! - Address bundling issue introduced in #​11412 where the react/cache internals ended up duplicated in the bundle. This was due to the fact that we had a react/hooks entrypoint that imported these files along with the newly introduced createQueryPreloader function, which lived outside of the react/hooks folder.

  • #​11371 ebd8fe2 Thanks @​phryneas! - Clarify types of EntityStore.makeCacheKey.

v3.8.10

Compare Source

Patch Changes
  • #​11489 abfd02a Thanks @​gronxb! - Fix networkStatus with useSuspenseQuery not properly updating to ready state when using a cache-and-network fetch policy that returns data equal to what is already in the cache.

  • #​11483 6394dda Thanks @​pipopotamasu! - Fix cache override warning output

v3.8.9

Compare Source

Patch Changes

v3.8.8

Compare Source

Patch Changes

v3.8.7

Compare Source

Patch Changes
  • #​11297 c8c76a522 Thanks @​jerelmiller! - Add an explicit return type for the useReadQuery hook called UseReadQueryResult. Previously the return type of this hook was inferred from the return value.

  • #​11337 bb1da8349 Thanks @​phryneas! - #​11206 used the TypeScript syntax infer X extends Y that was introduced in TS 4.8.
    This caused some problems for some users, so we are rolling back to a more backwars-compatible (albeit slightly less performant) type.

v3.8.6

Compare Source

Patch Changes
  • #​11291 2be7eafe3 Thanks @​ArioA! - Fix a bug that allows to only call loadErrorMessages without also calling loadDevErrorMessages.

  • #​11274 b29f000f3 Thanks @​jerelmiller! - Start the query ref auto dispose timeout after the initial promise has settled. This prevents requests that run longer than the timeout duration from keeping the component suspended indefinitely.

  • #​11289 b5894dbf0 Thanks @​phryneas! - MockedProvider: default connectToDevTools to false in created ApolloClient instance.

    This will prevent the mocked ApolloClient instance from trying to connect to the DevTools, which would start a setTimeout that might keep running after a test has finished.

  • #​11206 dd2ce7687 Thanks @​phryneas! - cache.modify: Less strict types & new dev runtime warnings.

v3.8.5

Compare Source

v3.8.4

Compare Source

Patch Changes

v3.8.3

Compare Source

Patch Changes

v3.8.2

Compare Source

Patch Changes
  • #​10072 51045c336 Thanks @​Huulivoide! - Fixes race conditions in useReactiveVar that may prevent updates to the reactive variable from propagating through the hook.

  • #​11162 d9685f53c Thanks @​jerelmiller! - Ensures GraphQL errors returned in subscription payloads adhere to the errorPolicy set in client.subscribe(...) calls.

  • #​11134 96492e142 Thanks @​alessbell! - Use separate type imports in useSuspenseQuery and useBackgroundQuery to workaround SWC compiler issue.

  • #​11117 6b8198109 Thanks @​phryneas! - Adds a new devtools registration mechanism and tweaks the mechanism behind the
    "devtools not found" mechanic.

  • #​11186 f1d429f32 Thanks @​jerelmiller! - Fix an issue where race conditions when rapidly switching between variables would sometimes result in the wrong data returned from the query. Specifically this occurs when a query is triggered with an initial set of variables (VariablesA), then triggers the same query with another set of variables (VariablesB) but switches back to the VariablesA before the response for VariablesB is returned. Previously this would result in the data for VariablesB to be displayed while VariablesA was active. The data is for VariablesA is now properly returned.

  • #​11163 a8a9e11e9 Thanks @​bignimbus! - Fix typo in error message: "occured" -> "occurred"

  • #​11180 7d9c481e5 Thanks @​jerelmiller! - Fixes an issue where refetching from useBackgroundQuery via refetch with an error after an error was already fetched would get stuck in a loading state.

v3.8.1

Compare Source

Patch Changes
  • #​11141 c469b1616 Thanks @​jerelmiller! - Remove newly exported response iterator helpers that caused problems on some installs where @types/node was not available.

    IMPORTANT

    The following exports were added in version 3.8.0 that are removed with this patch.

    • isAsyncIterableIterator
    • isBlob
    • isNodeReadableStream
    • isNodeResponse
    • isReadableStream
    • `isStr

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 these updates again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

@renovate renovate bot added the 📦 v15 Apply this label to a pull request, if it has to be cherry-picked to the v15.x-branch after merging. label Feb 24, 2022
@ZauberNerd
Copy link
Contributor

Blocked by: apollographql/apollo-client#9108

@renovate renovate bot force-pushed the renovate/release-bot/next-v15.x-apollo-graphql-packages branch from 5c3d735 to ed1a3e1 Compare March 1, 2022 17:15
@renovate renovate bot changed the title fix: update dependency @apollo/client to v3.5.9 (release-bot/next-v15.x) fix: update dependency @apollo/client to v3.5.10 (release-bot/next-v15.x) Mar 1, 2022
@renovate renovate bot force-pushed the renovate/release-bot/next-v15.x-apollo-graphql-packages branch from ed1a3e1 to 1d1a3cb Compare April 6, 2022 13:13
@renovate renovate bot force-pushed the renovate/release-bot/next-v15.x-apollo-graphql-packages branch 2 times, most recently from e9bb006 to acb3ae5 Compare April 26, 2022 22:19
@renovate renovate bot changed the title fix: update dependency @apollo/client to v3.5.10 (release-bot/next-v15.x) fix: update dependency @apollo/client to v3.6.0 (release-bot/next-v15.x) Apr 27, 2022
@renovate renovate bot force-pushed the renovate/release-bot/next-v15.x-apollo-graphql-packages branch from acb3ae5 to d855e37 Compare April 29, 2022 12:12
@renovate renovate bot changed the title fix: update dependency @apollo/client to v3.6.0 (release-bot/next-v15.x) fix: update dependency @apollo/client to v3.6.1 (release-bot/next-v15.x) Apr 29, 2022
@renovate renovate bot force-pushed the renovate/release-bot/next-v15.x-apollo-graphql-packages branch from d855e37 to 02891fb Compare May 3, 2022 01:00
@renovate renovate bot changed the title fix: update dependency @apollo/client to v3.6.1 (release-bot/next-v15.x) fix: update dependency @apollo/client to v3.6.2 (release-bot/next-v15.x) May 3, 2022
@renovate renovate bot force-pushed the renovate/release-bot/next-v15.x-apollo-graphql-packages branch from 02891fb to 834a042 Compare May 17, 2022 00:47
@renovate renovate bot changed the title fix: update dependency @apollo/client to v3.6.2 (release-bot/next-v15.x) fix: update dependency @apollo/client to v3.6.4 (release-bot/next-v15.x) May 17, 2022
@renovate renovate bot force-pushed the renovate/release-bot/next-v15.x-apollo-graphql-packages branch from 834a042 to 0e23d73 Compare May 23, 2022 23:26
@renovate renovate bot changed the title fix: update dependency @apollo/client to v3.6.4 (release-bot/next-v15.x) fix: update dependency @apollo/client to v3.6.5 (release-bot/next-v15.x) May 24, 2022
@renovate renovate bot force-pushed the renovate/release-bot/next-v15.x-apollo-graphql-packages branch from 0e23d73 to 4d740fb Compare May 31, 2022 16:35
@renovate renovate bot changed the title fix: update dependency @apollo/client to v3.6.5 (release-bot/next-v15.x) fix: update dependency @apollo/client to v3.6.6 (release-bot/next-v15.x) May 31, 2022
@renovate renovate bot force-pushed the renovate/release-bot/next-v15.x-apollo-graphql-packages branch from 4d740fb to fd1be1f Compare June 10, 2022 19:03
@renovate renovate bot changed the title fix: update dependency @apollo/client to v3.6.6 (release-bot/next-v15.x) fix: update dependency @apollo/client to v3.6.7 (release-bot/next-v15.x) Jun 10, 2022
@renovate renovate bot force-pushed the renovate/release-bot/next-v15.x-apollo-graphql-packages branch from fd1be1f to 9c1fee6 Compare June 13, 2022 19:31
@renovate renovate bot changed the title fix: update dependency @apollo/client to v3.6.7 (release-bot/next-v15.x) fix: update dependency @apollo/client to v3.6.8 (release-bot/next-v15.x) Jun 13, 2022
@renovate renovate bot force-pushed the renovate/release-bot/next-v15.x-apollo-graphql-packages branch 2 times, most recently from 3f13293 to f4715ae Compare June 22, 2022 20:49
@renovate renovate bot changed the title fix: update dependency @apollo/client to v3.6.8 (release-bot/next-v15.x) fix: update dependency @apollo/client to v3.6.9 (release-bot/next-v15.x) Jun 22, 2022
@renovate renovate bot force-pushed the renovate/release-bot/next-v15.x-apollo-graphql-packages branch from f4715ae to e72d50e Compare November 20, 2022 17:24
@renovate renovate bot changed the title fix: update dependency @apollo/client to v3.6.9 (release-bot/next-v15.x) fix: update dependency @apollo/client to v3.7.1 (release-bot/next-v15.x) Nov 20, 2022
@renovate renovate bot force-pushed the renovate/release-bot/next-v15.x-apollo-graphql-packages branch from e72d50e to a8d716a Compare March 18, 2023 20:07
@renovate renovate bot changed the title fix: update dependency @apollo/client to v3.9.1 (release-bot/next-v15.x) fix: update dependency @apollo/client to v3.9.2 (release-bot/next-v15.x) Feb 1, 2024
@renovate renovate bot force-pushed the renovate/release-bot/next-v15.x-apollo-graphql-packages branch from c1c731f to e858322 Compare February 6, 2024 21:30
@renovate renovate bot changed the title fix: update dependency @apollo/client to v3.9.2 (release-bot/next-v15.x) fix: update dependency @apollo/client to v3.9.3 (release-bot/next-v15.x) Feb 6, 2024
@renovate renovate bot force-pushed the renovate/release-bot/next-v15.x-apollo-graphql-packages branch from e858322 to 82a7f32 Compare February 7, 2024 18:23
@renovate renovate bot changed the title fix: update dependency @apollo/client to v3.9.3 (release-bot/next-v15.x) fix: update dependency @apollo/client to v3.9.4 (release-bot/next-v15.x) Feb 7, 2024
@renovate renovate bot force-pushed the renovate/release-bot/next-v15.x-apollo-graphql-packages branch from 82a7f32 to 64b2802 Compare February 15, 2024 19:17
@renovate renovate bot changed the title fix: update dependency @apollo/client to v3.9.4 (release-bot/next-v15.x) fix: update dependency @apollo/client to v3.9.5 (release-bot/next-v15.x) Feb 15, 2024
@renovate renovate bot force-pushed the renovate/release-bot/next-v15.x-apollo-graphql-packages branch from 64b2802 to aa5980c Compare March 6, 2024 19:41
@renovate renovate bot changed the title fix: update dependency @apollo/client to v3.9.5 (release-bot/next-v15.x) fix: update dependency @apollo/client to v3.9.6 (release-bot/next-v15.x) Mar 6, 2024
@renovate renovate bot force-pushed the renovate/release-bot/next-v15.x-apollo-graphql-packages branch from aa5980c to c346c40 Compare March 13, 2024 19:23
@renovate renovate bot changed the title fix: update dependency @apollo/client to v3.9.6 (release-bot/next-v15.x) fix: update dependency @apollo/client to v3.9.7 (release-bot/next-v15.x) Mar 13, 2024
@renovate renovate bot force-pushed the renovate/release-bot/next-v15.x-apollo-graphql-packages branch from c346c40 to 9229395 Compare March 20, 2024 21:06
@renovate renovate bot changed the title fix: update dependency @apollo/client to v3.9.7 (release-bot/next-v15.x) fix: update dependency @apollo/client to v3.9.8 (release-bot/next-v15.x) Mar 20, 2024
@renovate renovate bot force-pushed the renovate/release-bot/next-v15.x-apollo-graphql-packages branch from 9229395 to d141b44 Compare March 22, 2024 21:11
@renovate renovate bot changed the title fix: update dependency @apollo/client to v3.9.8 (release-bot/next-v15.x) fix: update dependency @apollo/client to v3.9.9 (release-bot/next-v15.x) Mar 22, 2024
@renovate renovate bot force-pushed the renovate/release-bot/next-v15.x-apollo-graphql-packages branch from d141b44 to 987f922 Compare April 1, 2024 21:51
@renovate renovate bot changed the title fix: update dependency @apollo/client to v3.9.9 (release-bot/next-v15.x) fix: update dependency @apollo/client to v3.9.10 (release-bot/next-v15.x) Apr 1, 2024
@renovate renovate bot force-pushed the renovate/release-bot/next-v15.x-apollo-graphql-packages branch from 987f922 to f175da9 Compare April 10, 2024 16:59
@renovate renovate bot changed the title fix: update dependency @apollo/client to v3.9.10 (release-bot/next-v15.x) fix: update dependency @apollo/client to v3.9.11 (release-bot/next-v15.x) Apr 10, 2024
@renovate renovate bot force-pushed the renovate/release-bot/next-v15.x-apollo-graphql-packages branch from f175da9 to e67793b Compare April 24, 2024 17:33
@renovate renovate bot changed the title fix: update dependency @apollo/client to v3.9.11 (release-bot/next-v15.x) fix: update dependency @apollo/client to v3.10.0 (release-bot/next-v15.x) Apr 24, 2024
@renovate renovate bot force-pushed the renovate/release-bot/next-v15.x-apollo-graphql-packages branch from e67793b to 90e6bd4 Compare April 24, 2024 19:55
@renovate renovate bot changed the title fix: update dependency @apollo/client to v3.10.0 (release-bot/next-v15.x) fix: update dependency @apollo/client to v3.10.1 (release-bot/next-v15.x) Apr 24, 2024
@renovate renovate bot force-pushed the renovate/release-bot/next-v15.x-apollo-graphql-packages branch from 90e6bd4 to 37eaeda Compare May 3, 2024 16:48
@renovate renovate bot changed the title fix: update dependency @apollo/client to v3.10.1 (release-bot/next-v15.x) fix: update dependency @apollo/client to v3.10.2 (release-bot/next-v15.x) May 3, 2024
@renovate renovate bot force-pushed the renovate/release-bot/next-v15.x-apollo-graphql-packages branch from 37eaeda to d2ac189 Compare May 7, 2024 17:09
@renovate renovate bot changed the title fix: update dependency @apollo/client to v3.10.2 (release-bot/next-v15.x) fix: update dependency @apollo/client to v3.10.3 (release-bot/next-v15.x) May 7, 2024
@renovate renovate bot force-pushed the renovate/release-bot/next-v15.x-apollo-graphql-packages branch from d2ac189 to 1e25461 Compare May 15, 2024 10:31
@renovate renovate bot changed the title fix: update dependency @apollo/client to v3.10.3 (release-bot/next-v15.x) fix: update dependency @apollo/client to v3.10.4 (release-bot/next-v15.x) May 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
✋ blocked 📦 v15 Apply this label to a pull request, if it has to be cherry-picked to the v15.x-branch after merging.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant