Update Apollo GraphQL packages #5140

hash-worker · 2024-09-14T12:23:03Z

This PR contains the following updates:

Package	Type	Update	Change
@apollo/client (source)	dependencies	minor	`3.10.5` -> `3.12.8`
apollo-server-core (source)	dependencies	minor	`3.12.1` -> `3.13.0`
apollo-server-errors (source)	dependencies	replacement	`3.3.1` -> `4.0.0`
apollo-server-express (source)	dependencies	minor	`3.9.0` -> `3.13.0`

Warning

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

This is a special PR that replaces apollo-server-errors with the community suggested minimal stable replacement version.

Release Notes

apollographql/apollo-client (@apollo/client)

`v3.12.8`

Compare Source

Patch Changes

#12292 3abd944 Thanks @phryneas! - Remove unused dependency response-iterator
#12287 bf313a3 Thanks @phryneas! - Fixes an issue where client.watchFragment/useFragment with @includes crashes when a separate cache update writes to the conditionally included fields.

`v3.12.7`

Compare Source

Patch Changes

#12281 d638ec3 Thanks @jerelmiller! - Make fatal tranport-level errors from multipart subscriptions available to the error link with the protocolErrors property.
```
const errorLink = onError(({ protocolErrors }) => {
  if (protocolErrors) {
    console.log(protocolErrors);
  }
});
```
#12281 d638ec3 Thanks @jerelmiller! - Fix the array type for the errors field on the ApolloPayloadResult type. This type was always in the shape of the GraphQL error format, per the multipart subscriptions protocol and never a plain string or a JavaScript error object.

`v3.12.6`

Compare Source

Patch Changes

#12267 d57429d Thanks @jerelmiller! - Maintain the TData type when used with Unmasked when TData is not a masked type generated from GraphQL Codegen.
#12270 3601246 Thanks @jerelmiller! - Fix handling of tagged/branded primitive types when used as scalar values with Unmasked.

`v3.12.5`

Compare Source

Patch Changes

#12252 cb9cd4e Thanks @jerelmiller! - Changes the default behavior of the MaybeMasked type to preserve types unless otherwise specified. This change makes it easier to upgrade from older versions of the client where types could have unexpectedly changed in the application due to the default of trying to unwrap types into unmasked types. This change also fixes the compilation performance regression experienced when simply upgrading the client since types are now preserved by default.

A new mode option has now been introduced to allow for the old behavior. See the next section on migrating if you wish to maintain the old default behavior after upgrading to this version.

Migrating from <= v3.12.4

If you've adopted data masking and have opted in to using masked types by setting the enabled property to true, you can remove this configuration entirely:

-declare module "@&#8203;apollo/client" {
-  interface DataMasking {
-    mode: "unmask"
-  }
-}

If you prefer to specify the behavior explicitly, change the property from enabled: true, to mode: "preserveTypes":

declare module "@&#8203;apollo/client" {
  interface DataMasking {
-    enabled: true
+    mode: "preserveTypes"
  }
}

If you rely on the default behavior in 3.12.4 or below and would like to continue to use unmasked types by default, set the mode to unmask:

declare module "@&#8203;apollo/client" {
  interface DataMasking {
    mode: "unmask";
  }
}

`v3.12.4`

Compare Source

Patch Changes

#12236 4334d30 Thanks @charpeni! - Fix an issue with refetchQueries where comparing DocumentNodes internally by references could lead to an unknown query, even though the DocumentNode was indeed an active query—with a different reference.

`v3.12.3`

Compare Source

Patch Changes

#12214 8bfee88 Thanks @phryneas! - Data masking: prevent infinite recursion of ContainsFragmentsRefs type
#12204 851deb0 Thanks @jerelmiller! - Fix Unmasked unwrapping tuple types into an array of their subtypes.
#12204 851deb0 Thanks @jerelmiller! - Ensure MaybeMasked does not try and unwrap types that contain index signatures.
#12204 851deb0 Thanks @jerelmiller! - Ensure MaybeMasked does not try to unwrap the type as Unmasked if the type contains any.

`v3.12.2`

Compare Source

Patch Changes

#12175 84af347 Thanks @jerelmiller! - Update peer deps to allow for React 19 stable release.

`v3.12.1`

Compare Source

Patch Changes

#12171 e1efe74 Thanks @phryneas! - Fix import extension in masking entry point.

`v3.12.0`

Compare Source

Minor Changes

Data masking 🎭

#12042 1c0ecbf Thanks @jerelmiller! - Introduces data masking in Apollo Client.

Data masking enforces that only the fields requested by the query or fragment is available to that component. Data masking is best paired with colocated fragments.

To enable data masking in Apollo Client, set the dataMasking option to true.
```
new ApolloClient({
  dataMasking: true,
  // ... other options
});
```
For detailed information on data masking, including how to incrementally adopt it in an existing applications, see the data masking documentation.
#12131 21c3f08 Thanks @jerelmiller! - Allow null as a valid from value in useFragment.

More Patch Changes

#12126 d10d702 Thanks @jerelmiller! - Maintain the existing document if its unchanged by the codemod and move to more naive whitespace formatting
#12150 9ed1e1e Thanks @jerelmiller! - Fix issue when using Unmasked with older versions of TypeScript when used with array fields.
#12116 8ae6e4e Thanks @jerelmiller! - Prevent field accessor warnings when using @unmask(mode: "migrate") on objects that are passed into cache.identify.
#12120 6a98e76 Thanks @jerelmiller! - Provide a codemod that applies @unmask to all named fragments for all operations and fragments.

Learn how to use the codemod in the incremental adoption documentation.
#12134 cfaf4ef Thanks @jerelmiller! - Fix issue where data went missing when an unmasked fragment in migrate mode selected fields that the parent did not.
#12154 d933def Thanks @phryneas! - Data masking types: handle overlapping nested array types and fragments on interface types.
#12139 5a53e15 Thanks @phryneas! - Fix issue where masked data would sometimes get returned when the field was part of a child fragment from a fragment unmasked by the parent query.
#12123 8422a30 Thanks @jerelmiller! - Warn when using data masking with "no-cache" operations.
#12139 5a53e15 Thanks @phryneas! - Fix issue where the warning emitted by @unmask(mode: "migrate") would trigger unnecessarily when the fragment was used alongside a masked fragment inside an inline fragment.
#12114 1d4ce00 Thanks @jerelmiller! - Fix error when combining @unmask and @defer directives on a fragment spread when data masking is enabled.
#12130 1e7d009 Thanks @jerelmiller! - Fix error thrown when applying unmask migrate mode warnings on interface types with selection sets that contain inline fragment conditions.
#12152 78137ec Thanks @phryneas! - Add a helper that will skip the TS unmasking alorithm when no fragments are present on type level
#12126 d10d702 Thanks @jerelmiller! - Ensure documents unchanged by the codemod are left untouched.
#12133 a6ece37 Thanks @jerelmiller! - Ensure null is retained in nullable types when unmasking a type with the Unmasked helper type.
#12139 5a53e15 Thanks @phryneas! - Fix issue that threw errors when masking partial data with @unmask(mode: "migrate").

`v3.11.10`

Compare Source

Patch Changes

#12093 1765668 Thanks @mgmolisani! - Fixed a bug when evaluating the devtools flag with the new syntax devtools.enabled that could result to true when explicitly set to false.

`v3.11.9`

Compare Source

Patch Changes

#12110 a3f95c6 Thanks @jerelmiller! - Fix an issue where errors returned from a fetchMore call from a Suspense hook would cause a Suspense boundary to be shown indefinitely.

`v3.11.8`

Compare Source

Patch Changes

#12054 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

#12052 e471cef Thanks @jerelmiller! - Fixes a regression from where passing an invalid identifier to from in useFragment would result in the warning TypeError: Cannot read properties of undefined (reading '__typename').

`v3.11.6`

Compare Source

Patch Changes

#12049 9c26892 Thanks @phryneas and @maciesielka! - Fix a bug where useFragment did not re-render as expected
#12044 04462a2 Thanks @DoctorJohn! - Cache the useSubscription hook's restart function definition between re-renders.

`v3.11.5`

Compare Source

Patch Changes

#12027 eb3e21b Thanks @JavaScriptBach! - Type MutationResult.reset as an arrow function
#12020 82d8cb4 Thanks @jerelmiller! - Better conform to Rules of React by avoiding write of ref in render for useFragment.

`v3.11.4`

Compare Source

Patch Changes

#11994 41b17e5 Thanks @jerelmiller! - Update the Modifier function type to allow cache.modify to return deeply partial data.
#11989 e609156 Thanks @phryneas! - Fix a potential crash when calling clearStore while a query was running.

Previously, calling client.clearStore() while a query was running had one of these results:
- useQuery would stay in a loading: true state.
- useLazyQuery would stay in a loading: 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 the useLazyQuery execute function will return a result in an error state.
#11994 41b17e5 Thanks @jerelmiller! - Prevent accidental distribution on cache.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 the data property with an errorPolicy of none.
#11974 c95848e Thanks @jerelmiller! - Fix an issue where fetchMore would write its result data to the cache when using it with a no-cache fetch policy.
#11974 c95848e Thanks @jerelmiller! - Fix an issue where executing fetchMore with a no-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 a no-cache fetch policy, fetchMore will now throw if an updateQuery function is not provided. This provides a mechanism to merge the results from the fetchMore call with the query's previous result.

`v3.11.2`

Compare Source

Patch Changes

#11980 38c0a2c Thanks @jerelmiller! - Fix missing getServerSnapshot error when using useSubscription on the server.

`v3.11.1`

Compare Source

Patch Changes

#12093 1765668 Thanks @mgmolisani! - Fixed a bug when evaluating the devtools flag with the new syntax devtools.enabled that could result to true when explicitly set to false.

`v3.11.0`

Compare Source

Potentially Breaking Fixes

#11789 5793301 Thanks @phryneas! - Changes usages of the GraphQLError type to GraphQLFormattedError.

This was a type bug - these errors were never GraphQLError instances
to begin with, and the GraphQLError class has additional properties that can
never 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 types
are for use on the server only, but don't get transported over the network.
#11626 228429a Thanks @phryneas! - Call nextFetchPolicy with "variables-changed" even if there is a fetchPolicy specified.

Previously this would only be called when the current fetchPolicy was equal to the fetchPolicy option or the option was not specified. If you use nextFetchPolicy 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 initial fetchPolicy, even when you specified a nextFetchPolicy function. If you previously relied on this behavior, you will need to update your nextFetchPolicy callback function to implement this resetting behavior.

As an example, if your code looked like the following:
```
useQuery(QUERY, {
  nextFetchPolicy(currentFetchPolicy, info) {
    // your logic here
  }
);
```
Update your function to the following to reimplement the resetting behavior:
```
useQuery(QUERY, {
  nextFetchPolicy(currentFetchPolicy, info) {
    if (info.reason === 'variables-changed') {
      return info.initialFetchPolicy;
    }
    // your logic here
  }
);
```

Minor Changes

#11923 d88c7f8 Thanks @jerelmiller! - Add support for subscribeToMore function to useQueryRefHandlers.
#11854 3812800 Thanks @jcostello-atlassian! - Support extensions in useSubscription
#11923 d88c7f8 Thanks @jerelmiller! - Add support for subscribeToMore function to useLoadableQuery.
#11863 98e44f7 Thanks @phryneas! - Reimplement useSubscription to fix rules of React violations.
#11869 a69327c Thanks @phryneas! - Rewrite big parts of useQuery and useLazyQuery 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 the connectToDevtools option in favor of a new devtools configuration.
```
new ApolloClient({
  devtools: {
    enabled: true,
    name: "Test Client",
  },
});
```
This option is backwards-compatible with connectToDevtools and will be used in the absense of a devtools option.
#11923 d88c7f8 Thanks @jerelmiller! - Add support for subscribeToMore function to useBackgroundQuery.
#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 to peerDependencies
#11927 2941824 Thanks @phryneas! - Add restart function to useSubscription.
#11949 4528918 Thanks @alessbell! - Remove deprecated watchFragment option, canonizeResults
#11937 78332be Thanks @phryneas! - createSchemaFetch: simulate serialized errors instead of an ApolloError instance
#11902 96422ce Thanks @phryneas! - Add cause field to ApolloError.
#11806 8df6013 Thanks @phryneas! - MockLink: add query default variables if not specified in mock request
#11926 3dd6432 Thanks @phryneas! - watchFragment: forward additional options to diffOptions
#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! - Allow IgnoreModifier to be returned from a optimisticResponse function when inferring from a TypedDocumentNode when used with a generic argument.
#11954 4a6e86a Thanks @phryneas! - Document (and deprecate) the previously undocumented errors property on the useQuery QueryResult type.
#11719 09a6677 Thanks @phryneas! - Allow wrapping createQueryPreloader
#11921 70406bf Thanks @phryneas! - add ignoreResults option to useSubscription

`v3.10.8`

Compare Source

Patch Changes

#11911 1f0460a Thanks @jerelmiller! - Allow undefined to be returned from a cache.modify modifier function when a generic type argument is used.

`v3.10.7`

Compare Source

Patch Changes

#11901 10a8c0a Thanks @phryneas! - update canUseLayoutEffect check to also allow for layout effects in React Native
#11861 1aed0e8 Thanks @henryqdineen! - Defend against non-serializable params in invariantWrappers
#11905 29755da Thanks @phryneas! - Add .d.cts files for cjs bundles
#11906 d104759 Thanks @phryneas! - chore: update TypeScript to 5.5

`v3.10.6`

Compare Source

Patch Changes

#11900 f745558 Thanks @phryneas! - useMutation: use useIsomorphicLayoutEffect instead of useLayoutEffect

apollographql/apollo-server (apollo-server-core)

`v3.13.0`

Compare Source

apollographql/apollo-server (apollo-server-express)

Configuration

📅 Schedule: Branch creation - "before 4am every weekday,every weekend" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ 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 Renovate Bot.

github-actions · 2025-01-30T17:15:32Z

Benchmark results

@rust/hash-graph-benches – Integrations

scaling_read_entity_complete_zero_depth

Function	Value	Mean	Flame graphs
entity_by_id	25 entities	$$3.44 \mathrm{ms} \pm 14.1 \mathrm{μs}\left({\color{gray}-0.851 \mathrm{\%}}\right) $$	Flame Graph
entity_by_id	1 entities	$$2.01 \mathrm{ms} \pm 8.69 \mathrm{μs}\left({\color{gray}-0.757 \mathrm{\%}}\right) $$	Flame Graph
entity_by_id	5 entities	$$2.03 \mathrm{ms} \pm 8.35 \mathrm{μs}\left({\color{gray}-0.333 \mathrm{\%}}\right) $$	Flame Graph
entity_by_id	10 entities	$$2.13 \mathrm{ms} \pm 11.2 \mathrm{μs}\left({\color{gray}-3.843 \mathrm{\%}}\right) $$	Flame Graph
entity_by_id	50 entities	$$4.11 \mathrm{ms} \pm 30.8 \mathrm{μs}\left({\color{gray}-0.730 \mathrm{\%}}\right) $$	Flame Graph

representative_read_entity

Function	Value	Mean	Flame graphs
entity_by_id	entity type ID: `https://blockprotocol.org/@alice/types/entity-type/playlist/v/1`	$$17.0 \mathrm{ms} \pm 194 \mathrm{μs}\left({\color{lightgreen}-27.941 \mathrm{\%}}\right) $$	Flame Graph
entity_by_id	entity type ID: `https://blockprotocol.org/@alice/types/entity-type/building/v/1`	$$17.1 \mathrm{ms} \pm 171 \mathrm{μs}\left({\color{lightgreen}-27.898 \mathrm{\%}}\right) $$	Flame Graph
entity_by_id	entity type ID: `https://blockprotocol.org/@alice/types/entity-type/book/v/1`	$$16.9 \mathrm{ms} \pm 215 \mathrm{μs}\left({\color{gray}1.41 \mathrm{\%}}\right) $$	Flame Graph
entity_by_id	entity type ID: `https://blockprotocol.org/@alice/types/entity-type/page/v/2`	$$17.1 \mathrm{ms} \pm 221 \mathrm{μs}\left({\color{gray}3.71 \mathrm{\%}}\right) $$	Flame Graph
entity_by_id	entity type ID: `https://blockprotocol.org/@alice/types/entity-type/person/v/1`	$$16.7 \mathrm{ms} \pm 228 \mathrm{μs}\left({\color{gray}-2.658 \mathrm{\%}}\right) $$	Flame Graph
entity_by_id	entity type ID: `https://blockprotocol.org/@alice/types/entity-type/organization/v/1`	$$16.9 \mathrm{ms} \pm 236 \mathrm{μs}\left({\color{gray}2.14 \mathrm{\%}}\right) $$	Flame Graph
entity_by_id	entity type ID: `https://blockprotocol.org/@alice/types/entity-type/uk-address/v/1`	$$16.2 \mathrm{ms} \pm 254 \mathrm{μs}\left({\color{gray}1.75 \mathrm{\%}}\right) $$	Flame Graph
entity_by_id	entity type ID: `https://blockprotocol.org/@alice/types/entity-type/block/v/1`	$$16.3 \mathrm{ms} \pm 171 \mathrm{μs}\left({\color{gray}4.78 \mathrm{\%}}\right) $$	Flame Graph
entity_by_id	entity type ID: `https://blockprotocol.org/@alice/types/entity-type/song/v/1`	$$16.0 \mathrm{ms} \pm 189 \mathrm{μs}\left({\color{gray}1.62 \mathrm{\%}}\right) $$	Flame Graph

representative_read_entity_type

Function	Value	Mean	Flame graphs
get_entity_type_by_id	Account ID: `d4e16033-c281-4cde-aa35-9085bf2e7579`	$$2.15 \mathrm{ms} \pm 5.61 \mathrm{μs}\left({\color{gray}-0.324 \mathrm{\%}}\right) $$	Flame Graph

representative_read_multiple_entities

Function	Value	Mean	Flame graphs
link_by_source_by_property	depths: DT=0, PT=2, ET=2, E=2	$$86.8 \mathrm{ms} \pm 374 \mathrm{μs}\left({\color{gray}-1.116 \mathrm{\%}}\right) $$	Flame Graph
link_by_source_by_property	depths: DT=0, PT=0, ET=2, E=2	$$82.7 \mathrm{ms} \pm 298 \mathrm{μs}\left({\color{gray}-2.300 \mathrm{\%}}\right) $$	Flame Graph
link_by_source_by_property	depths: DT=0, PT=0, ET=0, E=2	$$74.2 \mathrm{ms} \pm 351 \mathrm{μs}\left({\color{gray}-1.635 \mathrm{\%}}\right) $$	Flame Graph
link_by_source_by_property	depths: DT=2, PT=2, ET=2, E=2	$$91.0 \mathrm{ms} \pm 388 \mathrm{μs}\left({\color{gray}-0.408 \mathrm{\%}}\right) $$	Flame Graph
link_by_source_by_property	depths: DT=255, PT=255, ET=255, E=255	$$99.2 \mathrm{ms} \pm 406 \mathrm{μs}\left({\color{gray}-0.910 \mathrm{\%}}\right) $$	Flame Graph
link_by_source_by_property	depths: DT=0, PT=0, ET=0, E=0	$$39.0 \mathrm{ms} \pm 237 \mathrm{μs}\left({\color{gray}-1.359 \mathrm{\%}}\right) $$	Flame Graph
entity_by_property	depths: DT=0, PT=2, ET=2, E=2	$$53.1 \mathrm{ms} \pm 240 \mathrm{μs}\left({\color{gray}0.082 \mathrm{\%}}\right) $$	Flame Graph
entity_by_property	depths: DT=0, PT=0, ET=2, E=2	$$48.5 \mathrm{ms} \pm 189 \mathrm{μs}\left({\color{gray}-0.250 \mathrm{\%}}\right) $$	Flame Graph
entity_by_property	depths: DT=0, PT=0, ET=0, E=2	$$42.8 \mathrm{ms} \pm 104 \mathrm{μs}\left({\color{gray}-0.402 \mathrm{\%}}\right) $$	Flame Graph
entity_by_property	depths: DT=2, PT=2, ET=2, E=2	$$56.7 \mathrm{ms} \pm 254 \mathrm{μs}\left({\color{gray}-0.375 \mathrm{\%}}\right) $$	Flame Graph
entity_by_property	depths: DT=255, PT=255, ET=255, E=255	$$66.1 \mathrm{ms} \pm 307 \mathrm{μs}\left({\color{gray}-0.342 \mathrm{\%}}\right) $$	Flame Graph
entity_by_property	depths: DT=0, PT=0, ET=0, E=0	$$39.0 \mathrm{ms} \pm 199 \mathrm{μs}\left({\color{gray}-4.385 \mathrm{\%}}\right) $$	Flame Graph

scaling_read_entity_complete_one_depth

Function	Value	Mean	Flame graphs
entity_by_id	25 entities	$$83.6 \mathrm{ms} \pm 436 \mathrm{μs}\left({\color{lightgreen}-52.930 \mathrm{\%}}\right) $$	Flame Graph
entity_by_id	1 entities	$$21.0 \mathrm{ms} \pm 80.1 \mathrm{μs}\left({\color{gray}-0.434 \mathrm{\%}}\right) $$	Flame Graph
entity_by_id	5 entities	$$27.5 \mathrm{ms} \pm 273 \mathrm{μs}\left({\color{gray}1.70 \mathrm{\%}}\right) $$	Flame Graph
entity_by_id	10 entities	$$58.0 \mathrm{ms} \pm 185 \mathrm{μs}\left({\color{red}81.4 \mathrm{\%}}\right) $$	Flame Graph
entity_by_id	50 entities	$$5.40 \mathrm{s} \pm 541 \mathrm{ms}\left({\color{gray}0.496 \mathrm{\%}}\right) $$	Flame Graph

scaling_read_entity_linkless

Function	Value	Mean	Flame graphs
entity_by_id	100 entities	$$2.21 \mathrm{ms} \pm 12.8 \mathrm{μs}\left({\color{gray}3.29 \mathrm{\%}}\right) $$	Flame Graph
entity_by_id	1000 entities	$$3.18 \mathrm{ms} \pm 15.0 \mathrm{μs}\left({\color{red}7.34 \mathrm{\%}}\right) $$	Flame Graph
entity_by_id	10000 entities	$$13.8 \mathrm{ms} \pm 75.9 \mathrm{μs}\left({\color{gray}-1.277 \mathrm{\%}}\right) $$	Flame Graph
entity_by_id	1 entities	$$2.02 \mathrm{ms} \pm 7.54 \mathrm{μs}\left({\color{gray}0.010 \mathrm{\%}}\right) $$	Flame Graph
entity_by_id	10 entities	$$2.02 \mathrm{ms} \pm 8.00 \mathrm{μs}\left({\color{gray}-0.783 \mathrm{\%}}\right) $$	Flame Graph

hash-worker bot enabled auto-merge September 14, 2024 12:23

hashdotai previously approved these changes Sep 14, 2024

View reviewed changes

hash-worker bot assigned CiaranMn Sep 14, 2024

vercel bot had a problem deploying to Preview – hashdotdesign September 14, 2024 13:04 Failure

vercel bot deployed to Preview – hashdotdev September 14, 2024 13:09 View deployment

vercel bot had a problem deploying to Preview – hash September 14, 2024 13:13 Failure

hash-worker bot dismissed hashdotai’s stale review via c7f13cd September 14, 2024 15:17

hash-worker bot force-pushed the deps/js/apollo-graphql-packages branch from 5b21aa8 to c7f13cd Compare September 14, 2024 15:17

hashdotai previously approved these changes Sep 14, 2024

View reviewed changes

vercel bot had a problem deploying to Preview – hash September 14, 2024 15:55 Failure

vercel bot deployed to Preview – hashdotdev September 14, 2024 16:00 View deployment

vercel bot had a problem deploying to Preview – hashdotdesign September 14, 2024 16:00 Failure

vercel bot had a problem deploying to Preview – hash September 14, 2024 17:36 Failure

vercel bot deployed to Preview – hashdotdev September 14, 2024 17:40 View deployment

vercel bot had a problem deploying to Preview – hashdotdesign September 14, 2024 17:42 Failure

hash-worker bot force-pushed the deps/js/apollo-graphql-packages branch from 96d25cd to bef7601 Compare September 14, 2024 23:16

vercel bot had a problem deploying to Preview – hashdotdesign September 14, 2024 23:21 Failure

vercel bot deployed to Preview – hashdotdev September 14, 2024 23:21 View deployment

vercel bot had a problem deploying to Preview – hash September 14, 2024 23:21 Failure

vilkinsons changed the title ~~Update Apollo GraphQL packages~~ H-3340: Update Apollo GraphQL packages Sep 20, 2024

hash-worker bot force-pushed the deps/js/apollo-graphql-packages branch from bef7601 to d091354 Compare September 23, 2024 05:24

hash-worker bot changed the title ~~H-3340: Update Apollo GraphQL packages~~ Update Apollo GraphQL packages Sep 23, 2024

vercel bot had a problem deploying to Preview – hashdotdesign September 23, 2024 05:29 Failure

vercel bot had a problem deploying to Preview – hash January 22, 2025 17:13 Failure

vercel bot deployed to Preview – hashdotdev January 22, 2025 17:15 View deployment

hash-worker bot force-pushed the deps/js/apollo-graphql-packages branch from a38ceb6 to 1711787 Compare January 24, 2025 12:49

vercel bot had a problem deploying to Preview – hashdotdesign January 24, 2025 13:01 Failure

vercel bot deployed to Preview – hashdotdev January 24, 2025 13:02 View deployment

vercel bot had a problem deploying to Preview – hash January 24, 2025 13:05 Failure

hash-worker bot dismissed hashdotai’s stale review via 713ea3b January 25, 2025 02:48

hash-worker bot force-pushed the deps/js/apollo-graphql-packages branch from 1711787 to 713ea3b Compare January 25, 2025 02:48

hashdotai previously approved these changes Jan 25, 2025

View reviewed changes

vercel bot had a problem deploying to Preview – hashdotdesign January 25, 2025 02:51 Failure

vercel bot had a problem deploying to Preview – hash January 25, 2025 02:52 Failure

vercel bot deployed to Preview – hashdotdev January 25, 2025 02:54 View deployment

hash-worker bot force-pushed the deps/js/apollo-graphql-packages branch from 713ea3b to 9277430 Compare January 28, 2025 11:09

vercel bot deployed to Preview – hashdotdev January 28, 2025 11:38 View deployment

vercel bot had a problem deploying to Preview – hashdotdesign January 28, 2025 11:39 Failure

vercel bot had a problem deploying to Preview – hash January 28, 2025 11:42 Failure

hash-worker bot dismissed hashdotai’s stale review via 9fba921 January 28, 2025 17:38

hash-worker bot force-pushed the deps/js/apollo-graphql-packages branch from 9277430 to 9fba921 Compare January 28, 2025 17:38

hashdotai previously approved these changes Jan 28, 2025

View reviewed changes

vercel bot had a problem deploying to Preview – hashdotdesign January 28, 2025 17:41 Failure

vercel bot deployed to Preview – hashdotdev January 28, 2025 17:43 View deployment

vercel bot had a problem deploying to Preview – hash January 28, 2025 17:43 Failure

Update Apollo GraphQL packages

d74139c

hash-worker bot dismissed hashdotai’s stale review via d74139c January 30, 2025 16:41

hash-worker bot force-pushed the deps/js/apollo-graphql-packages branch from 9fba921 to d74139c Compare January 30, 2025 16:41

hashdotai approved these changes Jan 30, 2025

View reviewed changes

vercel bot had a problem deploying to Preview – hash January 30, 2025 16:44 Failure

vercel bot deployed to Preview – hashdotdev January 30, 2025 16:45 View deployment

vercel bot had a problem deploying to Preview – hashdotdesign January 30, 2025 16:47 Failure

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Update Apollo GraphQL packages #5140

Update Apollo GraphQL packages #5140

hash-worker bot commented Sep 14, 2024 •

edited

Loading

github-actions bot commented Jan 30, 2025

@rust/hash-graph-benches – Integrations

scaling_read_entity_complete_zero_depth

representative_read_entity

representative_read_entity_type

representative_read_multiple_entities

scaling_read_entity_complete_one_depth

scaling_read_entity_linkless

Update Apollo GraphQL packages #5140

Are you sure you want to change the base?

Update Apollo GraphQL packages #5140

Conversation

hash-worker bot commented Sep 14, 2024 • edited Loading

Release Notes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Migrating from <= v3.12.4

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Minor Changes

Data masking 🎭

More Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Potentially disruptive change

Patch Changes

Patch Changes

Potentially Breaking Fixes

Minor Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Configuration

github-actions bot commented Jan 30, 2025

Benchmark results

@rust/hash-graph-benches – Integrations

scaling_read_entity_complete_zero_depth

representative_read_entity

representative_read_entity_type

representative_read_multiple_entities

scaling_read_entity_complete_one_depth

scaling_read_entity_linkless

hash-worker bot commented Sep 14, 2024 •

edited

Loading