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

Update Apollo GraphQL packages #91

Closed
wants to merge 3 commits into from

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Mar 31, 2023

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@apollo/client (source) 3.7.3 -> 3.7.17 age adoption passing confidence
@apollo/client (source) 3.7.4 -> 3.7.17 age adoption passing confidence
@apollo/gateway ^0.43.1 -> ^0.54.0 age adoption passing confidence
apollo-server 3.11.1 -> 3.12.0 age adoption passing confidence

⚠ Dependency Lookup Warnings ⚠

Warnings were logged while processing this repo. Please check the Dependency Dashboard for more information.


Release Notes

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

v3.7.17

Compare Source

Patch Changes

v3.7.16

Compare Source

Patch Changes

v3.7.15

Compare Source

Patch Changes
  • #​10891 ab42a5c08 Thanks @​laverdet! - Fixes a bug in how multipart responses are read when using @defer. When reading a multipart body, HttpLink no longer attempts to parse the boundary (e.g. "---" or other boundary string) within the response data itself, only when reading the beginning of each mulitpart chunked message.

  • #​10789 23a4e1578 Thanks @​phryneas! - Fix a bug where other fields could be aliased to __typename or id, in which case an incoming result would be merged into the wrong cache entry.

v3.7.14

Compare Source

Patch Changes
  • #​10764 1b0a61fe5 Thanks @​phryneas! - Deprecate useFragment returnPartialData option

  • #​10810 a6252774f Thanks @​dleavitt! - Fix type signature of ServerError.

    In <3.7 HttpLink and BatchHttpLink would return a ServerError.message of e.g. "Unexpected token 'E', \"Error! Foo bar\" is not valid JSON" and a ServerError.result of undefined in the case where a server returned a >= 300 response code with a response body containing a string that could not be parsed as JSON.

    In >=3.7, message became e.g. Response not successful: Received status code 302 and result became the string from the response body, however the type in ServerError.result was not updated to include the string type, which is now properly reflected.

v3.7.13

Compare Source

Patch Changes
  • #​10805 a5503666c Thanks @​phryneas! - Fix a potential memory leak in SSR scenarios when many persistedQuery instances were created over time.

  • #​10718 577c68bdd Thanks @​Hsifnus! - Delay Concast subscription teardown slightly in useSubscription to prevent unexpected Concast teardown when one useSubscription hook tears down its in-flight Concast subscription immediately followed by another useSubscription hook reusing and subscribing to that same Concast

v3.7.12

Compare Source

Patch Changes

v3.7.11

Compare Source

Patch Changes
  • #​10586 4175af594 Thanks @​alessbell! - Improve WebSocket error handling for generic Event received on error. For more information see https://developer.mozilla.org/en-US/docs/Web/API/WebSocket/error_event.

  • #​10411 152baac34 Thanks @​lovasoa! - Simplify error message generation and make 'undefined' an impossible message string.

  • #​10592 cdb98ae08 Thanks @​alessbell! - Adds support for multipart subscriptions in HttpLink.

  • #​10698 38508a251 Thanks @​jerelmiller! - Changes the behavior of useLazyQuery introduced in #​10427 where unmounting a component before a query was resolved would reject the promise with an abort error. Instead, the promise will now resolve naturally with the result from the request.

    Other notable fixes:

    • Kicking off multiple requests in parallel with the execution function will now ensure each returned promise is resolved with the data from its request. Previously, each promise was resolved with data from the last execution.
    • Re-rendering useLazyQuery with a different query document will now ensure the execution function uses the updated query document. Previously, only the query document rendered the first time would be used for the request.
  • #​10660 364bee98f Thanks @​alessbell! - Upgrades TypeScript to v5. This change is fully backward-compatible and transparent to users.

  • #​10597 8fb9d190d Thanks @​phryneas! - Fix a bug where an incoming cache update could prevent future updates from the active link.

  • #​10629 02605bb3c Thanks @​phryneas! - useQuery: delay unsubscribe to fix race conditions

v3.7.10

Compare Source

Patch Changes
  • #​9438 52a9c8ea1 Thanks @​dciesielkiewicz! - Ensure the client option passed to useMutation's execute function is used when provided. Previously this option was ignored.

  • #​9124 975b923c0 Thanks @​andrebrantom! - Make ApolloClient.writeQuery and ApolloClient.writeFragment behave more like cache.writeQuery and cache.writeFragment by returning the reference returned by the cache.

v3.7.9

Compare Source

Patch Changes
  • #​10560 a561ecf43 Thanks @​benjamn! - Keep __typename fragment when it does not contain @client directive and strip out inline fragments which use a @client directive. Thanks @​Gazler and @​mtsmfm!

  • #​10560 251a12806 Thanks @​benjamn! - Refactor removeDirectivesFromDocument to fix AST ordering sensitivities and avoid 1/3 AST traversals, potentially improving performance for large queries

v3.7.8

Compare Source

Patch Changes
  • #​7555 45562d6fa Thanks @​TheCeloReis! - Adds TVariables generic to GraphQLRequest and MockedResponse interfaces.

  • #​10526 1d13de4f1 Thanks @​benjamn! - Tolerate undefined concast.sources if complete called earlier than concast.start

  • #​10497 8a883d8a1 Thanks @​nevir! - Update SingleExecutionResult and IncrementalPayload's data types such that they no longer include undefined, which was not a valid runtime value, to fix errors when TypeScript's exactOptionalPropertyTypes is enabled.

v3.7.7

Compare Source

Patch Changes
  • #​10502 315faf9ca Thanks @​jerelmiller! - Log a warning to the console when a mock passed to MockedProvider or MockLink cannot be matched to a query during a test. This makes it easier to debug user errors in the mock setup, such as typos, especially if the query under test is using an errorPolicy set to ignore, which makes it difficult to know that a match did not occur.

  • #​10499 9e54f5dfa Thanks @​phryneas! - Allow the execution function returned by useLazyQuery to change the query.

  • #​10362 14a56b105 Thanks @​mccraveiro! - Fix error when server returns an error and we are also querying for a local field

v3.7.6

Compare Source

Patch Changes
  • #​10470 47435e879 Thanks @​alessbell! - Bumps TypeScript to 4.9.4 (previously 4.7.4) and updates types to account for changes in TypeScript 4.8 by propagating contstraints on generic types. Technically this makes some types stricter as attempting to pass null|undefined into certain functions is now disallowed by TypeScript, but these were never expected runtime values in the first place.
    This should only affect you if you are wrapping functions provided by Apollo Client with your own abstractions that pass in their generics as type arguments, in which case you might get an error like error TS2344: Type 'YourGenericType' does not satisfy the constraint 'OperationVariables'. In that case, make sure that YourGenericType is restricted to a type that only accepts objects via extends, like Record<string, any> or @apollo/client's OperationVariables:

    import {
      QueryHookOptions,
      QueryResult,
      useQuery,
    + OperationVariables,
    } from '@&#8203;apollo/client';
    - export function useWrappedQuery<T, TVariables>(
    + export function useWrappedQuery<T, TVariables extends OperationVariables>(
        query: DocumentNode,
        queryOptions: QueryHookOptions<T, TVariables>
      ): QueryResult<T, TVariables> {
        const [execute, result] = useQuery<T, TVariables>(query);
      }
  • #​10408 55ffafc58 Thanks @​zlrlo! - fix: modify BatchHttpLink to have a separate timer for each different batch key

  • #​9573 4a4f48dda Thanks @​vladar! - Improve performance of local resolvers by only executing selection sets that contain an @client directive. Previously, local resolvers were executed even when the field did not contain @client. While the result was properly discarded, the unncessary work could negatively affect query performance, sometimes signficantly.

v3.7.5

Compare Source

Patch Changes

v3.7.4

Compare Source

Patch Changes
apollographql/federation (@​apollo/gateway)

v0.54.1

Compare Source

v0.52.1

Compare Source

v0.52.0

Compare Source

v0.51.0

Compare Source

v0.50.2

Compare Source

v0.50.1

Compare Source

v0.50.0

Compare Source

v0.49.0

Compare Source

v0.48.3

Compare Source

v0.48.1

Compare Source

v0.48.0

Compare Source

v0.47.0

Compare Source

v0.46.0

Compare Source

v0.45.1

Compare Source

v0.45.0

Compare Source

v0.44.1

Compare Source

v0.44.0

Compare Source

apollographql/apollo-server (apollo-server)

v3.12.0

Compare Source


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.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


  • 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
Copy link
Author

renovate bot commented Mar 31, 2023

⚠ Artifact update problem

Renovate failed to update an artifact 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:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json
npm ERR! code E404
npm ERR! 404 Not Found - GET https://registry.npmjs.org/collaborrate-docs-generator - Not found
npm ERR! 404 
npm ERR! 404  'collaborrate-docs-generator@^0.6.0' is not in this registry.
npm ERR! 404 
npm ERR! 404 Note that you can also install from a
npm ERR! 404 tarball, folder, http url, or git url.

npm ERR! A complete log of this run can be found in: /tmp/worker/1f31d9/56c602/cache/others/npm/_logs/2023-07-09T08_03_50_982Z-debug-0.log

@netlify
Copy link

netlify bot commented Mar 31, 2023

Deploy Preview for alternatedemo failed.

Name Link
🔨 Latest commit c841dd3
🔍 Latest deploy log https://app.netlify.com/sites/alternatedemo/deploys/6426f006e7dfab0008681940

@renovate renovate bot force-pushed the renovate/apollo-graphql-packages branch from 21255f9 to c841dd3 Compare March 31, 2023 14:36
@renovate renovate bot force-pushed the renovate/apollo-graphql-packages branch from c841dd3 to c243c47 Compare June 14, 2023 05:38
@renovate renovate bot force-pushed the renovate/apollo-graphql-packages branch from c243c47 to ae09043 Compare June 22, 2023 05:29
@renovate renovate bot force-pushed the renovate/apollo-graphql-packages branch from ae09043 to a6c3b7d Compare June 29, 2023 23:49
@renovate renovate bot force-pushed the renovate/apollo-graphql-packages branch from a6c3b7d to a11cde0 Compare July 7, 2023 23:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant