Update Apollo GraphQL packages #10

renovate · 2023-06-26T23:17:57Z

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@apollo/server (source)	`4.7.4` -> `4.10.4`
@apollo/subgraph (source)	`2.4.8` -> `2.7.8`

Release Notes

apollographql/apollo-server (@apollo/server)

`v4.10.4`

Compare Source

Patch Changes

#7871 18a3827 Thanks @tninesling! - Subscription heartbeats are initialized prior to awaiting subscribe(). This allows long-running setup to happen in the returned Promise without the subscription being terminated prior to resolution.

`v4.10.3`

Compare Source

Patch Changes

#7866 5f335a5 Thanks @tninesling! - Catch errors thrown by subscription generators, and gracefully clean up the subscription instead of crashing.

`v4.10.2`

Compare Source

Patch Changes

#7849 c7e514c Thanks @TylerBloom! - In the subscription callback server plugin, terminating a subscription now immediately closes the internal async generator. This avoids that generator existing after termination and until the next message is received.

`v4.10.1`

Compare Source

Patch Changes

#7843 72f568e Thanks @bscherlein! - Improves timing of the willResolveField end hook on fields which return Promises resolving to Arrays. This makes the use of the setCacheHint method more reliable.

`v4.10.0`

Compare Source

Minor Changes

#7786 869ec98 Thanks @ganemone! - Restore missing v1 skipValidation option as dangerouslyDisableValidation. Note that enabling this option exposes your server to potential security and unexpected runtime issues. Apollo will not support issues that arise as a result of using this option.
#7803 e9a0d6e Thanks @favna! - allow stringifyResult to return a Promise<string>

Users who implemented the stringifyResult hook can now expect error responses to be formatted with the hook as well. Please take care when updating to this version to ensure this is the desired behavior, or implement the desired behavior accordingly in your stringifyResult hook. This was considered a non-breaking change as we consider that it was an oversight in the original PR that introduced stringifyResult hook.

Patch Changes

#7793 9bd7748 Thanks @bnjjj! - General availability of subscription callback protocol
#7799 63dc50f Thanks @stijnbe! - Fix type of ApolloServerPluginUsageReporting reportTimer
#7740 fe68c1b Thanks @barnisanov! - Uninstalled body-parser and used express built-in body-parser functionality instead(mainly the json middleware)

`v4.9.5`

Compare Source

Patch Changes

#7741 07585fe39 Thanks @mayakoneval! - Pin major releases of embeddable Explorer & Sandbox code.
#7769 4fac1628c Thanks @cwikla! - Change SchemaReporter.pollTimer from being a NodeJS.Timer to a NodeJS.Timeout

`v4.9.4`

Compare Source

Patch Changes

#7747 ddce036e1 Thanks @trevor-scheer! - The minimum version of graphql officially supported by Apollo Server 4 as a peer dependency, v16.6.0, contains a serious bug that can crash your Node server. This bug is fixed in the immediate next version, graphql@16.7.0, and we strongly encourage you to upgrade your installation of graphql to at least v16.7.0 to avoid this bug. (For backwards compatibility reasons, we cannot change Apollo Server 4's minimum peer dependency, but will change it when we release Apollo Server 5.)

Apollo Server 4 contained a particular line of code that makes triggering this crashing bug much more likely. This line was already removed in Apollo Server v3.8.2 (see #6398) but the fix was accidentally not included in Apollo Server 4. We are now including this change in Apollo Server 4, which will reduce the likelihood of hitting this crashing bug for users of graphql v16.6.0. That said, taking this @apollo/server upgrade does not prevent this bug from being triggered in other ways, and the real fix to this crashing bug is to upgrade graphql.

`v4.9.3`

Compare Source

Patch Changes

a1c725eaf Thanks @trevor-scheer! - Ensure API keys are valid header values on startup

Apollo Server previously performed no sanitization or validation of API keys on startup. In the case that an API key was provided which contained characters that are invalid as header values, Apollo Server could inadvertently log the API key in cleartext.

This only affected users who:
- Provide an API key with characters that are invalid as header values
- Use either schema or usage reporting
- Use the default fetcher provided by Apollo Server or configure their own node-fetch fetcher
Apollo Server now trims whitespace from API keys and validates that they are valid header values. If an invalid API key is provided, Apollo Server will throw an error on startup.

For more details, see the security advisory:
GHSA-j5g3-5c8r-7qfx

`v4.9.2`

Compare Source

Patch Changes

#7699 62e7d940d Thanks @trevor-scheer! - Fix error path attachment for list items

Previously, when errors occurred while resolving a list item, the trace builder would fail to place the error at the correct path and just default to the root node with a warning message:

Could not find node with path x.y.1, defaulting to put errors on root node.

This change places these errors at their correct paths and removes the log.

`v4.9.1`

Compare Source

Patch Changes

#7672 ebfde0007 Thanks @trevor-scheer! - Add missing nonce on script tag for non-embedded landing page

`v4.9.0`

Compare Source

Minor Changes

#7617 4ff81ca50 Thanks @trevor-scheer! - Introduce new ApolloServerPluginSubscriptionCallback plugin. This plugin implements the subscription callback protocol which is used by Apollo Router. This feature implements subscriptions over HTTP via a callback URL which Apollo Router registers with Apollo Server. This feature is currently in preview and is subject to change.

You can enable callback subscriptions like so:
```
import { ApolloServerPluginSubscriptionCallback } from '@&#8203;apollo/server/plugin/subscriptionCallback';
import { ApolloServer } from '@&#8203;apollo/server';

const server = new ApolloServer({
  // ...
  plugins: [ApolloServerPluginSubscriptionCallback()],
});
```
Note that there is currently no tracing or metrics mechanism in place for callback subscriptions. Additionally, this plugin "intercepts" callback subscription requests and bypasses some of Apollo Server's internals. The result of this is that certain plugin hooks (notably executionDidStart and willResolveField) will not be called when handling callback subscription requests or when sending subscription events.

For more information on the subscription callback protocol, visit the docs:
https://www.apollographql.com/docs/router/executing-operations/subscription-callback-protocol/

Patch Changes

#7659 4784f46fb Thanks @renovate! - Update graphql-http dependency

`v4.8.1`

Compare Source

Patch Changes

#7636 42fc65cb2 Thanks @trevor-scheer! - Update test suite for compatibility with Node v20

`v4.8.0`

Compare Source

Minor Changes

#7634 f8a8ea08f Thanks @dfperry5! - Updating the ApolloServer constructor to take in a stringifyResult function that will allow a consumer to pass in a function that formats the result of an http query.

Usage:
```
const server = new ApolloServer({
  typeDefs,
  resolvers,
  stringifyResult: (value: FormattedExecutionResult) => {
    return JSON.stringify(value, null, 2);
  },
});
```

`v4.7.5`

Compare Source

Patch Changes

#7614 4fadf3ddc Thanks @Cellule! - Publish TypeScript typings for CommonJS modules output.

This allows TypeScript projects that use CommonJS modules with
moduleResolution: "node16" or
moduleResolution: "nodeNext"
to correctly resolves the typings of apollo's packages as CommonJS instead of ESM.
Updated dependencies [4fadf3ddc]:
- @apollo/cache-control-types @1.0.3
- @apollo/server-gateway-interface @1.1.1
- @apollo/usage-reporting-protobuf @4.1.1

apollographql/federation (@apollo/subgraph)

`v2.7.8`

Compare Source

Patch Changes

Triggering a clean 2.7.8 release now that harmonizer build has been fixed. (#3010)
Updated dependencies [2ad72802044310a528e8944f4538efe519424504]:
- @apollo/federation-internals @2.7.8

`v2.7.7`

Compare Source

Patch Changes

No logical changes since 2.7.5 or 2.7.6, but we fixed a bug in the release process, so we need to publish a new patch version (2.7.7). (#2999)
Updated dependencies [bee0b0828b4fb6a1d3172ac330560e2ab6c046bb]:
- @apollo/federation-internals @2.7.7

`v2.7.6`

Compare Source

Patch Changes

Updated dependencies []:
- @apollo/federation-internals @2.7.6

`v2.7.5`

Compare Source

Patch Changes

Updated dependencies []:
- @apollo/federation-internals @2.7.5

Minor Changes

Implement progressive @override functionality (#2911)

The progressive @override feature brings a new argument to the @override directive: label: String. When a label is added to an @override application, the override becomes conditional, depending on parameters provided to the query planner (a set of which labels should be overridden). Note that this feature will be supported in router for enterprise users only.

Out-of-the-box, the router will support a percentage-based use case for progressive @override. For example:
```
type Query {
  hello: String @&#8203;override(from: "original", label: "percent(5)")
}
```
The above example will override the root hello field from the "original" subgraph 5% of the time.

More complex use cases will be supported by the router via the use of coprocessors/rhai to resolve arbitrary labels to true/false values (i.e. via a feature flag service).

Patch Changes

Updated dependencies [6ae42942b13dccd246ccc994faa2cb36cd62cb3c, 66833fb8d04c9376f6ed476fed6b1ca237f477b7, 931f87c6766c7439936df706727cbdc0cd6bcfd8]:
- @apollo/federation-internals @2.7.0

`v2.6.3`

Compare Source

Patch Changes

Updated dependencies []:
- @apollo/federation-internals @2.6.3

`v2.6.2`

Compare Source

Patch Changes

Updated dependencies [7b5b836d15247c997712a47847f603aa5887312e, 74ca7dd617927a20d79b824851f7651ef3c40a4e]:
- @apollo/federation-internals @2.6.2

`v2.6.1`

Compare Source

Patch Changes

Updated dependencies [0d5ab01a]:
- @apollo/federation-internals @2.6.1

`v2.6.0`

Compare Source

Patch Changes

Updated dependencies [b18841be, e325b499]:
- @apollo/federation-internals @2.6.0

`v2.5.7`

Compare Source

Patch Changes

Updated dependencies []:
- @apollo/federation-internals @2.5.7

`v2.5.6`

Compare Source

Patch Changes

Updated dependencies [c719214a]:
- @apollo/federation-internals @2.5.6

`v2.5.5`

Compare Source

Patch Changes

Fix specific case for requesting __typename on interface entity type (#2775)

In certain cases, when resolving a __typename on an interface entity (due to it actual being requested in the operation), that fetch group could previously be trimmed / treated as useless. At a glance, it appears to be a redundant step, i.e.:
```
{ ... on Product { __typename id }} => { ... on Product { __typename} }
```
It's actually necessary to preserve this in the case that we're coming from an interface object to an (entity) interface so that we can resolve the concrete __typename correctly.
Updated dependencies []:
- @apollo/federation-internals @2.5.5

`v2.5.4`

Compare Source

Patch Changes

Updated dependencies []:
- @apollo/federation-internals @2.5.4

`v2.5.3`

Compare Source

Patch Changes

Updated dependencies [4b9a512b, c6e0e76d, 1add932c]:
- @apollo/federation-internals @2.5.3

`v2.5.2`

Compare Source

Patch Changes

Updated dependencies [35179f08]:
- @apollo/federation-internals @2.5.2

`v2.5.1`

Compare Source

Patch Changes

Updated dependencies [b9052fdd]:
- @apollo/federation-internals @2.5.1

`v2.5.0`

Compare Source

Minor Changes

Introduce the new @authenticated directive for composition (#2644)

Note that this directive will only be fully supported by the Apollo Router as a GraphOS Enterprise feature at runtime. Also note that composition of valid @authenticated directive applications will succeed, but the resulting supergraph will not be executable by the Gateway or an Apollo Router which doesn't have the GraphOS Enterprise entitlement.

Users may now compose @authenticated applications from their subgraphs into a supergraph. This addition will support a future version of Apollo Router that enables authenticated access to specific types and fields via directive applications.

The directive is defined as follows:
```
directive @&#8203;authenticated on
  | FIELD_DEFINITION
  | OBJECT
  | INTERFACE
  | SCALAR
  | ENUM
```
In order to compose your @authenticated usages, you must update your subgraph's federation spec version to v2.5 and add the @authenticated import to your existing imports like so:
```
@&#8203;link(url: "https://specs.apollo.dev/federation/v2.5", import: [..., "@&#8203;authenticated"])
```

Patch Changes

Updated dependencies [fe1e3d7b, 6b18af50, 9396c0d6, 2b5796a9, 4f3c3b9e]:
- @apollo/federation-internals @2.5.0

`v2.4.13`

Compare Source

Patch Changes

Updated dependencies []:
- @apollo/federation-internals @2.4.13

`v2.4.12`

Compare Source

Patch Changes

Updated dependencies [693c2433]:
- @apollo/federation-internals @2.4.12

`v2.4.11`

Compare Source

Patch Changes

Updated dependencies [a740e071]:
- @apollo/federation-internals @2.4.11

`v2.4.10`

Compare Source

Patch Changes

Updated dependencies [b6be9f96]:
- @apollo/federation-internals @2.4.10

`v2.4.9`

Compare Source

Patch Changes

Updated dependencies [7ac83456, d60349b3, 1bb7c512, 02eab3ac, fd4545c2]:
- @apollo/federation-internals @2.4.9

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 bot changed the title ~~Update dependency @apollo/server to v4.7.5~~ Update Apollo GraphQL packages Jul 7, 2023

renovate bot force-pushed the renovate/apollo-graphql-packages branch from 4f7f7dd to b8012c0 Compare July 7, 2023 23:56

renovate bot force-pushed the renovate/apollo-graphql-packages branch 5 times, most recently from abbf707 to f57ffcb Compare July 22, 2023 02:37

renovate bot force-pushed the renovate/apollo-graphql-packages branch from f57ffcb to 20ec7ea Compare July 28, 2023 02:06

renovate bot force-pushed the renovate/apollo-graphql-packages branch from 20ec7ea to bc36266 Compare August 5, 2023 08:13

renovate bot force-pushed the renovate/apollo-graphql-packages branch 3 times, most recently from 6e30155 to cc6c2a2 Compare September 1, 2023 05:52

renovate bot force-pushed the renovate/apollo-graphql-packages branch from cc6c2a2 to 7b78398 Compare September 19, 2023 05:46

renovate bot force-pushed the renovate/apollo-graphql-packages branch from 7b78398 to c5de2af Compare October 5, 2023 05:31

renovate bot force-pushed the renovate/apollo-graphql-packages branch from c5de2af to 148d6f0 Compare October 14, 2023 03:01

renovate bot force-pushed the renovate/apollo-graphql-packages branch from 148d6f0 to 7cb1757 Compare October 27, 2023 02:51

renovate bot force-pushed the renovate/apollo-graphql-packages branch from 7cb1757 to 36d6814 Compare November 17, 2023 11:34

renovate bot force-pushed the renovate/apollo-graphql-packages branch from 36d6814 to 8b14403 Compare November 28, 2023 08:28

renovate bot force-pushed the renovate/apollo-graphql-packages branch from 8b14403 to b33e07c Compare December 12, 2023 02:38

renovate bot force-pushed the renovate/apollo-graphql-packages branch from b33e07c to 2e38e12 Compare January 3, 2024 02:55

renovate bot force-pushed the renovate/apollo-graphql-packages branch from 2e38e12 to 63c95d9 Compare January 11, 2024 20:34

renovate bot force-pushed the renovate/apollo-graphql-packages branch 2 times, most recently from c83f70b to ac5bb11 Compare January 25, 2024 05:48

renovate bot force-pushed the renovate/apollo-graphql-packages branch from ac5bb11 to b2791a8 Compare March 7, 2024 20:53

renovate bot force-pushed the renovate/apollo-graphql-packages branch 2 times, most recently from 5a20b79 to b1b219d Compare March 23, 2024 02:48

renovate bot force-pushed the renovate/apollo-graphql-packages branch 3 times, most recently from 197a07a to da107cd Compare April 22, 2024 20:43

renovate bot force-pushed the renovate/apollo-graphql-packages branch from da107cd to bf1e3b9 Compare May 3, 2024 08:02

renovate bot force-pushed the renovate/apollo-graphql-packages branch 2 times, most recently from 9f3e904 to 59ff4d8 Compare May 10, 2024 23:51

Update Apollo GraphQL packages

7ae8d71

renovate bot force-pushed the renovate/apollo-graphql-packages branch from 59ff4d8 to 7ae8d71 Compare May 22, 2024 23:32

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Update Apollo GraphQL packages #10

Update Apollo GraphQL packages #10

renovate bot commented Jun 26, 2023 •

edited

Update Apollo GraphQL packages #10

Are you sure you want to change the base?

Update Apollo GraphQL packages #10

Conversation

renovate bot commented Jun 26, 2023 • edited

Release Notes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Configuration

renovate bot commented Jun 26, 2023 •

edited